All Things Microsoft > Microsoft as a Company
One line of html code to crash Winblows
mobrien_12:
Win 98, Mozilla 1.7.8, ATI Rage Pro Turbo, nothing happens.
Orethrius:
Strictly out of curiosity: did anyone else think to close everything else first before clicking that link? Here are my traceback questions to those of you who experienced a crash:
(1) Which Operating System (full version here, plus SP if Windows) did you test?
(2) Were the patches up-to-date?
(3) Which browser were you using?
(4) What kind of graphics card do you have?
(5) What were you doing when the crash occured?
I believe this is a kernel issue as well, but I may be wrong so it's a good idea to trace it back as far as possible.
MrX:
well, i don't think its ever going to load in FF for beos. it's probly just not 'stable enough' i guess but nothing crashes, nothing slows, no memory gets eaten up, but the scroll bars adjust as they should, even tho it still shows white after 2 minutes.
note- i was able to make my FF crash on BeOS by making a html file with 10000 pop ups on it. i would like to see what happens on winshit.
Lead Head:
My PC doens't even blue screen just freezes. But my Dell 5100 laptop with a mobility radeon 7500 blue screens and said there was a problem with the ATI driver
muzzy:
Doesn't crash my w2k3 box, and i don't have w2k test box available at the moment. It does however lag down the w2k3 significantly, a lot more than it should.
It doesn't really eat memory, just cpu. Huge loads of cpu. The whole thing makes me think this is an issue with GDI. Stuff just doesn't make sense here.
It's a serious issue anyway, I'll look into it a little.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version