All Things Microsoft > Microsoft as a Company
One line of html code to crash Winblows
toadlife:
If you think about it, this is sort of similar to the long time fork bomb vulnerability with linux. In both cases, the system involved comes without sane limits on how it uses it's resources. The result in both cases is the ability of any user to take down the system.
RaZoR1394:
--- Quote from: Combustible ---you are reading way too much into it, this isnt a bug the computer is doing what its supposed to do. maybe there should be some safeguards to stop it from trying to do that but thats not relevant right now, this is why is "crashes"
(it doesnt actually crash. let it sit long enough and it will recover unless the pc goes down under the strain)
the browser is being told to prep a 9999999x9999999 space for an image. thats 99999980000001 pixels.
thats a lot of pixels. an image of 262144x262144 is half a terabyte according to the gimp
you got a pc that can handle several orders of magnitude larger file sizes? probably not. if you try and render this, here is what happens:
1. it allots the space
2. it freaks out
3. it seems to lock up but really is just working super hard
4. your pc will go down if its not stable to begin with
im typing this on IE6 XPSP2 after having opened the link. it took me a while to get the mouse over the X to close the window and free up my pc, but i did it.
woo.
--- End quote ---
Off course It's a bug as the computer won't even lag when using GNU/Linux och *BSD.
MrX:
--- Quote from: Combustible ---you are reading way too much into it, this isnt a bug the computer is doing what its supposed to do. maybe there should be some safeguards to stop it from trying to do that but thats not relevant right now, this is why is "crashes"
(it doesnt actually crash. let it sit long enough and it will recover unless the pc goes down under the strain)
the browser is being told to prep a 9999999x9999999 space for an image. thats 99999980000001 pixels.
thats a lot of pixels. an image of 262144x262144 is half a terabyte according to the gimp
you got a pc that can handle several orders of magnitude larger file sizes? probably not. if you try and render this, here is what happens:
1. it allots the space
2. it freaks out
3. it seems to lock up but really is just working super hard
4. your pc will go down if its not stable to begin with
im typing this on IE6 XPSP2 after having opened the link. it took me a while to get the mouse over the X to close the window and free up my pc, but i did it.
woo.
--- End quote ---
sort of like what happens when you take a cpu intensive program like cpuburn and run two at once? or one at 'realtime' priority?
Mr X
Aloone_Jonez:
--- Quote from: RaZoR1394 ---Doesn't look like a nVidia issue. I've heard from a lot of people who have gotten the bluescreen or reboot with ATI cards. Some with nVidia cards also only get slowdowns and not BSOD/reboot.
Looks like kernel or driver issue. Still if It's a driver issue It's the fault of Windows because it lets the graphics driver run on "ring 0" (kernel level) which is idiotic. In other systems graphics drivers run on "ring 3" for ex X.
--- End quote ---
I've just realised what you meant, Windows is silly for running its Windowing system in kernel mode while the UNIX X-window system runs in user mode.
Well I can see your point but Windows NT is a purely graphical OS, it doesn't have a text mode like UNIX does. When X crashes under Linux it's just as bad as it takes out all X programs ie OpenOffice so still I loose my work anyway, though this has only happened to me on Redhat 9.0 though.
Combustible:
--- Quote from: RaZoR1394 ---Off course It's a bug as the computer won't even lag when using GNU/Linux och *BSD.
--- End quote ---
technically no, a bug is when something doesnt work... you cant compare behavior of windows to *nix as a basis for calling it a bug, those are two very different codebases. this is working as it was designed to work, it just needs safeguards to prevent it from trying to do what its being told to do.
i would therefore call it an exploit. a rather useless one but still an exploit.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version