Flash intermitently crashes FireFox 3.5

[Dave M G]

Binary package hint: firefox-3.5

I have seen bug reports about Flash crashing FireFox when in fullscreen mode, but that is not the case here.

In my case, web sites will crash FireFox 3.5.3 when changing to a new video, or navigating to a new page with Flash content, particularly Flash video content. The video does not have to be full screen, and it almost never is.

It doesn't always happen. It seems to be contingent on having been browsing for a while. My guess is that there is some kind of build up in memory, and after a certain threshold is reached, then FireFox crashes.

When I restart FireFox after such a crash, I can restore the pages I had, and the page that caused the crash will work just fine.

However, after some amount of browsing, eventually I will inevitably hit another page which causes a crash.

Unfortunately, the time it takes, or the number of pages with video content it takes to cause a crash varies, so I can not specify exact steps to cause a crash. But I can say with assurance that if I keep browsing and navigating from page to page, eventually hitting a Flash video page that causes a crash is a certainty.

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
NonfreeKernelModules: nvidia
Package: firefox-3.5 3.5.3+build1+nobinonly-0ubuntu0.9.04.2
ProcEnviron:
 PATH=(custom, user)
 LANG=ja_JP.UTF-8
 SHELL=/bin/bash
SourcePackage: firefox-3.5
Uname: Linux 2.6.28-15-generic i686

[Micah Gersten (micahg)]

Thank you for reporting this to Ubuntu. Does Firefox actually close? Can you submit a crash report?

[Dave M G (martin-autotelic)]

When this happens, FireFox closes completely. It does not give me any option to submit a crash report. The window simply, and abruptly, disappears from my desktop. If I have more than one window, they all disappear together.

[Micah Gersten (micahg)]

Thank you for reporting this to Ubuntu. Sometimes Firefox profiles can become corrupt and/or extensions can conflict. Could you please try this with a new profile and see if the problem still exists? You do not need to delete your old profile to test. If this helps, you might want to try to disable all your extensions and re-enable them one by one until you find the problematic one.

You can start the profile manager with the following command:
firefox-3.5 -ProfileManager

[vivia (vivia)]

I got a crash report which indicates UIM.

By the way, I have EXACTLY the same symptoms. I am trying to view some YouTube video, and then I click on another video before the first one ends, and it often crashes. Or, I am trying to book plane tickets on a webpage that uses Flash, which auto-refreshes. I thought it was Flash, tried export LD_PRELOAD=/usr/lib/libGL.so.1 and export XLIB_SKIP_ARGB_VISUALS=1 , it still crashes. Then I got this backtrace... and I'm more confused... is this in Firefox, gtk, flash, or uim?

Program received signal SIGSEGV, Segmentation fault.
0x008f0072 in g_type_check_instance_cast () from /usr/lib/libgobject-2.0.so.0
(gdb) bt full
#0 0x008f0072 in g_type_check_instance_cast ()
   from /usr/lib/libgobject-2.0.so.0
No symbol table info available.
#1 0x064c0f22 in ?? () from /usr/lib/gtk-2.0/2.10.0/immodules/im-uim.so
No symbol table info available.
#2 0x064c1b55 in ?? () from /usr/lib/gtk-2.0/2.10.0/immodules/im-uim.so
No symbol table info available.
#3 0x064c1c31 in ?? () from /usr/lib/gtk-2.0/2.10.0/immodules/im-uim.so
No symbol table info available.
#4 0x07328394 in gtk_im_context_focus_in () from /usr/lib/libgtk-x11-2.0.so.0
No symbol table info available.
#5 0x07328394 in gtk_im_context_focus_in () from /usr/lib/libgtk-x11-2.0.so.0
No symbol table info available.
#6 0x01651f3b in ?? () from /usr/lib/xulrunner-1.9.1.3/libxul.so
No symbol table info available.
#7 0x01657945 in ?? () from /usr/lib/xulrunner-1.9.1.3/libxul.so
No symbol table info available.
#8 0x01312716 in ?? () from /usr/lib/xulrunner-1.9.1.3/libxul.so
No symbol table info available.
#9 0x01091f5e in ?? () from /usr/lib/xulrunner-1.9.1.3/libxul.so
No symbol table info available.
#10 0x0109245d in ?? () from /usr/lib/xulrunner-1.9.1.3/libxul.so
No symbol table info available.

[AnthonyAldorasi (anthonyaldorasi)]

I had the same exact problem but I did this ( running amd 64 if that might help ), the flash plugin that you get with synaptic was causing my problems, ( unable to fast forward, seek, skip, load, etc ) so what I did was I went to the adobe site grabbed the libflashplugin.so for the 64bit arch and removed flash then copyed the new flash plugin into /usr/lib64/mozilla/plugins. And ever since then my firefox constantly crashes when sites have flash. This is what I get when running in a console.

(firefox:17015): Gdk-WARNING **: XID collision, trouble ahead

(firefox:17015): Gdk-WARNING **: XID collision, trouble ahead

(firefox:17015): Gdk-WARNING **: XID collision, trouble ahead

(firefox:17015): Gdk-WARNING **: XID collision, trouble ahead

(firefox:17015): Gdk-WARNING **: XID collision, trouble ahead
Segmentation fault (core dumped)

And thats it, and the same exact problem keeps happening with epiphany.

[Sylvain Orset (sylv1-deactivatedaccount)]

@all : I had the same problem with the latest 64 bits flash plugin downloaded from Adobe labs website. Reproduced with Firefox, Arora, Rekonq ... I solved it following the instructions here : http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=509018#70

Hope this helps,
Sylvain

[arneko (goblinpower)]

I am on a 32 bit system and also affected. How can I produce more debug output?
I can't compile the c file mentioned in the previous post - and I doubt that it would help, since I am neither on an 64 bit system nor do I have an old cpu.

Creating a new Profile doesn't help either.
I never experienced this with epiphany though.

[Micah Gersten (micahg)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 477513, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.