Closed Bug 192238 Opened 23 years ago Closed 23 years ago

OS crashed

Categories

(SeaMonkey :: General, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

CLOSED INVALID

People

(Reporter: waveangle, Assigned: asa)

References

()

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3a) Gecko/20021212 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3a) Gecko/20021212 OS crashed at the same time I was using the mouse wheel. Reproducible: Didn't try Steps to Reproduce: 1. go to a page that shows vertical scroll bar. 2. use the mouse wheel to go down 3. possible crash Actual Results: OS crashed completely, reboot required Expected Results: Scrolling normally Using proxomitron proxy, and atguard personal firewall.
if your OS crashed, perhaps your OS is at fault? :) this bugreport is not really usable, so i marked it INVALID.
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → INVALID
it's invalid because Mozilla can't crash win2k/NT/XP. It can only trigger a bug in your hardware or your driver
Status: RESOLVED → VERIFIED
I agree the bug is not too usable. But I thought you should get a sense of how unstable mozilla is and this is why I bothered. This type of os crash has happened a lot on my system with 1.2 and now 1.3a. Mozilla seems to be crashing my os at random. When I went back to mozilla 1.0.x the crash stopped happening. I can reproduce this crash if you like. If you don't want bug reports don't ask for them.
Hardware is stable otherwise. If its in a driver, this might as well be OS as far as the end user is concerned. I am not instrumented to track crashes in drivers. System is stable otherwise, failure could be in atguard firewall. I will turn off atguard and verify before sending in more bugs.
Bug is reproducible. Same url. Crash happens every time. System stable otherwise.
I installed the latest ATI Radeon video driver and the problem seems to be gone. No more crash.
Status: VERIFIED → CLOSED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.