Firefox crashes very often with Segmentation fault. Under Valgrind it does not crash, but shows a lot of messages like this: Invalid read of size 4 at 0x5997CF8: _XGetAtomName (in /usr/lib/libX11.so.6.2.0) by 0x5F46406: gdk_event_translate (in /usr/lib/libgdk-x11-2.0.so.0.1600.6) by 0x5F4733D: _gdk_events_queue (in /usr/lib/libgdk-x11-2.0.so.0.1600.6) by 0x5F4773E: gdk_event_dispatch (in /usr/lib/libgdk-x11-2.0.so.0.1600.6) by 0x58C9312: g_main_context_dispatch (in /usr/lib/libglib-2.0.so.0.2000.5) Address 0x970f128 is 24 bytes inside a block of size 25 alloc'd at 0x402947F: malloc (in /usr/lib/valgrind/x86-linux/vgpreload_memcheck.so) by 0x59A00BB: _XUpdateAtomCache (in /usr/lib/libX11.so.6.2.0) Reproducible: Sometimes Steps to Reproduce:
Firefox 3.5.4 seems stable (will report if further testing shows something else). Probably time to drop the old unstable version.
(In reply to comment #1) > Firefox 3.5.4 seems stable (will report if further testing shows something > else). Unfortunately Firefox 3.5.4 crashes on some webpages: bug #292651. Will try 3.5.5 soon.
Possibly this is related to bug #291727. If you start firefox from a terminal do you see XID collision messages before the segfault?
Firefox 3.6.3 seems stable (and does not seem to have bug #292651). A small test run with Valgrind did not reveal any Invalid reads (but some Conditional jump or move depends on uninitialized value(s)).
