bugzilla.mozilla.org will be intermittently unavailable on Saturday, March 24th, from 16:00 until 20:00 UTC.
From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.8) Gecko/20020204 BuildID: 20022020406 Whenever I attempt to resize the browser window, no matter which page I'm visiting, the entire system freezes, including mouse and keyboard. This has happened on this particular computer, both with Win98(first release with updates) and Win2k(sp2). I'm not sure if it's due to the fact that Trillian (www.ceruleanstudios.com - latest version) is running or not, since I can't remember if it happens when Trillian is not running. I haven't noticed it happen when on RedHat 7.2, but I haven't spent much time over there since that partition is fairly new and it's a different build of Mozilla. My husband and I were talking about possibilities of what might be causing this. We both use the same skin (modern) so I don't believe that's the cause. He doesn't use the tabs like I do, but it doesn't matter if I have tabs up in the Mozilla window or not. The only workaround I've found is to simply press the reset button on the tower. *sigh* I couldn't find this in the bug list at all. I'm a little surprised to be the only one experiencing this, especially since I just formatted and this is on a fresh install of Win2k. When I was in Win98, I expected the system to crash all the time. Reproducible: Sometimes Steps to Reproduce: 1.Open Mozilla. 2.Resize the window. 3.Watch the system lock up. Actual Results: The system freezes completely at this point. There is no mouse or keyboard functionality, nothing indicating the computer is trying to process something. It's basically just a screen shot of my desktop at that point. Expected Results: The screen should be resized and I should be able to continue to browse. Someone asked me if I used the Talkback agent to report this. Since there is a system-wide freeze, there's no possible way I could, or I would have. This pc is a dual boot Win2k (sp2) and RedHat 7.2. Same thing happened on this computer when it was just Win98. There's 240mb ram in the pc and plenty of drive space. It's a 1.2GHz Athlon. I'm completely stumped. The only thing I can come up with is the possibility of Trillian getting in the way.
I've noticed it's not only when Trillian is running but at other times as well. Also, it's not only when I'm resizing, but any time I click on that window now. I've uninstalled and will be reinstalling later. Let me know if there's anything else you want to know about my system. This is a clean install of Win2k. I thought it was just that I needed to format and clean out my system, but apparently I was mistaken. Thanks for the help. :)
What you describes almost sounds more like a hardware issue... Mozilla should not be able to do anything that brings down your system. Does your system ever freeze while not running Mozilla (especially running something else that uses a lot or RAM). The usual hardware culprit of system freeze would be video card (or memory). Make sure your video drivers are up to date.
Quite honestly, that's something I've considered. The system lockups were only when running Mozilla. My system hasn't had any difficulties that I can remember since I've uninstalled it. I can't imagine Mozilla would be more resource intensive than the graphics programs I run. I tested Mozilla without anything else running in the background and it still seemed to have issues. I'm checking on video drivers, that is certainly a good idea whether it is the cause or not. Thanks for the advice. I'm hoping it isn't a memory issue. I've been there before, but that was accompanied with many BSODs and other such grief. Even a dying fan can cause similar issues. We'll see what else I can dig up. Thanks again. :)
Another video-driver thing to try is (if it supports it) to turn off the accelerated features of the driver. You could also try using the generic VGA/SVGA (super low-res and color) driver. Mozilla will look horrible but might not crash.
mozilla can't hang windows Nt/2k/XP This must be a driver/hardware problem
Status: UNCONFIRMED → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.