371908 - FF 2.0.0.x crashes. Happens daily, but I don't know how to force it to happen

Status: RESOLVED WORKSFORME

(Firefox :: General, defect)

Description

[Jason Cornez]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.2) Gecko/20070226 Firefox/2.0.0.2
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.2) Gecko/20070226 Firefox/2.0.0.2

At seemingly random times, FF will crash.  The crash always occurs when I try to take some action with the browser - something as simply as clicking on a tab will do it.  That is, if I am not interacting with the browser at all, it doesn't just up and die on its own.  Mostly it is stable and the same action will not reproduce the problem for me.

When the crash occurs, I see the following in my terminal from where I started FF.

(Gecko:18450): Gdk-CRITICAL **: gdk_colormap_get_screen: assertion `GDK_IS_COLORMAP (cmap)' failed

(Gecko:18450): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed

(Gecko:18450): Gdk-CRITICAL **: gdk_colormap_get_visual: assertion `GDK_IS_COLORMAP (colormap)' failed
/usr/libexec/mozilla-launcher: line 119: 18450 Segmentation fault      $(type -P aoss) "$mozbin" "$@"
firefox-bin exited with non-zero status (139)


Reproducible: Sometimes

Steps to Reproduce:
1. Open browser and use it for some time
2. Possibly leave it idle (overnight for example)  [not sure this matters]
3. Possibly start a java applet [not sure this matters]
4. Use it a bit more and it crashes.
Actual Results:  
The browser crashed.  As in, the process stopped running entirely.

Expected Results:  
Normal operation.

I have definitely see the crash occur without leaving the browser idle overnight.

Comment 1

[Stephanie Daugherty [:sdaugherty]]

Did it give you a talkback report by any chance? If so, please paste the report ID.

Comment 2

[Jason Cornez]

Unfortunately, no.  The process just completely vanishes.  On subsequent restart, I'm asked if I want to start a new session or restore the old one.

Comment 3

[Sam Besselink]

Does this occur at moments where a GTK open-file dialog should appear? This might be a duplicate of #371387.

Sam.

Comment 4

[Jason Cornez]

Nope, definitely not.  Nor is it related to clicking on a link or opening a menu or anything like that.  It is just a matter of switching to firefox the application after using some other application.

It does seem to be related to having loaded a Java applet in the browser at some time in the past, but the crash has nothing to do with using the applet at the time of the crash.  To be sure, when I am returning to firefox (after reading an email or whatever), I am typically just clicking on a tab and then goodbye.  The contents of the tab don't matter.

I'm a gentoo user and I've recently discovered that firefox-bin is more stable than the one I compile myself.  If I can get a talkback report, I'll be sure to post it.  Talkback isn't available (of course) is the version I compile.

Comment 5

[Jason Cornez]

Attachment: Here are the details from what talkback captured.

Comment 6

[Wayne Mery (:wsmwk)]

do you still see this problem using FF 3.5 beta**, or FF 3.0 started in safe mode***?

If yes, please comment
If not, please close with resolution set to WORKSFORME or INVALID (if problem was extension or the like)

** http://www.mozilla.com/en-US/firefox/all-beta.html
*** http://support.mozilla.com/en-US/kb/Safe+Mode

Comment 7

[Jason Cornez]

I've been using FF 3.5 for some time and I haven't seen this problem.  Indeed it has been so long that I forgot all about this issue.