Summary: | Mozilla 1.2.1 randomly locks up X display hard | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | A. Permyakov <apermyakov> |
Component: | Current packages | Assignee: | Mozilla Gentoo Team <mozilla> |
Status: | RESOLVED INVALID | ||
Severity: | critical | CC: | Klaus.Kusche |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
A. Permyakov
2003-02-21 18:57:23 UTC
A note on hardware: the box is an older dual PPro machine, Intel PR440FX motherboard, Inno3D Tornado GeForce2 MX-400 PCI video card. If this is relevant, display manager is xfce-3.8.18-r2 I cannot complain of the same issues. Try to update gcc to 3.2.2, and remerge mozilla. Try a different kernel ? Upgraded gcc, recompiled Mozilla, problem persists. Will rebuild kernel next, although I do not quite understand what the kernel has to do with it. Anyway, I'll get to it this weekend and report back when I have more info. Thanks for your help -- Andrew. Upgraded to ~x86 across the board. portage-2.0.47-r7 gcc-3.2.2-r1 xfree-4.3.0 mozilla-1.3_beta Problem seems to have reslved itself. Of course, this does not help to determine the cause of the original problem. Thanks for your help. Hmmm, same or similar problem here: After using mozilla for some time, it suddenly goes up to 100 % CPU, does not react to keyboard or mouse input, and does not repaint its windows. However, I can still switch to an xterm and kill it, everything works normal afterwards. This is on an up-to-date, pre-1.4 Gentoo Linux with no ~ packages (gcc 3.1.1-R1, mozilla 1.2.1-r5). Some weeks ago, mozilla definitely didn't have that problem. Might be due to the xfree 4.2 -> 4.3 upgrade?! Since 1.2.1 is no longer relevant (1.4 is out, folks). This bug should be removed from bugzilla. AFAIK this is a non-issue with both the stable and unstable Mozilla builds of late. 1.4 is not yet marked "stable" and 1.3 has bugs which are showstoppers for me (see 19973). So 1.2 is still relevant. Unfortunately I, like Azarah didn't seem to encounter such issues. Additionally since the reporter confirmed that the problem went away once his environment was rebuilt, the circumstances are untennable. Hmmm, for me, the problem still exists for mozilla 1.4-r3: After a lot of browsing, mozilla suddenly starts using lots of CPU and mem and reacts very slowly. If I continue to use it, it locks up completely at 100% CPU and needs to be killed. Please reopen (or shall I create a new report?) |