Firefox XID collision causing Core Dump in Lucid

[Matt Eskes]

Binary package hint: firefox

Noticed that Firefox was crashing when trying to view certain websites in Lucid. Started firefox from command prompt in order to get debugging feedback which lead to:

meskes@Neptune:$ firefox
2.4+ kernel w/o ELF notes? -- report this

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

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

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

(firefox-bin:18871): Gdk-WARNING **: XID collision, trouble ahead
Segmentation fault (core dumped)
meskes@Neptune:

Now I have noticed one thing in common when this happens; the sites I'm trying to view, in this case a local new site had an embedded flash video. Don't know if that's got anything of anything to do with it, but I figured that I might add that for what good it may or may not do.

ProblemType: Bug
Architecture: amd64
AuditLog:

Date: Tue Mar 9 00:02:27 2010
DistroRelease: Ubuntu 10.04
FirefoxPackages:
 firefox 3.6+nobinonly-0ubuntu5
 firefox-gnome-support 3.6+nobinonly-0ubuntu5
 firefox-branding 3.6+nobinonly-0ubuntu5
 abroswer N/A
 abrowser-branding N/A
KernLog:

Package: firefox 3.6+nobinonly-0ubuntu5
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-15.22-generic
SourcePackage: firefox
Uname: Linux 2.6.32-15-generic x86_64

[William Glover (williamglover)]

I have the "Segmentation fault (core dumped)" also, however, it is the only error message I get. I have disabled all Addons in Firefox & uninstalled flashplugin-nonfree via apt, the crashes still occur.
I can reproduce the bug by opening several tabs with javascript content and clicking around the links a few times (in my case, reproduced on Wikipedia with monobook.js set up.) Hope this helps to pin down the Bug.

[Märt Suga (mart-suga)]

Same problem here.
However, I must add, it crushes almost every time I leave my computer. And when I come back, firefox has closed itself. No errors, just the "core dumped" message.

[Märt Suga (mart-suga)]

Well, after yesterday's (2010-03-24) updates (2.6.32-16 -> 2.6.32-17) and a reboot firefox seems to work correctly. Hasn't crashed since.

[supermalloch (supermalloch)]

when running firefox from terminal i quite the list of "Gdk-WARNING **: XID collision, trouble ahead". But i do not recieve the core dump error instead when mine crashes it causes a black flickering screen, that can only be fixed by holding down the power button until force reboot occurs. and when it reboots there is no apport error to report. :?

[William Glover (williamglover)]

I can confirm that the update on 2010-03-24 solved the firefox core dump problems.

However, it did cause a series of Kernel Panics for me that could only be solved by installing the upstream kernel. These crashes occured independently from firefox though. (see Bug #555730 for more)
Maybe that is what supermalloch is experiencing.

[William Glover (williamglover)]

Since the latest Firefox update, the Segmentation Error has returned for me. It now only displays "Segmentation Error" and closes Firefox when started from terminal, the other error messages seem to have disappeared.

[Øyvind Stegard (oyvindstegard)]

Getting seemingly spontaneous Firefox crashes with only a single segfault message in log. And before that a whole lot of XID collision Gdk-warnings. Fully updated Lucid, firefox 3.6.3+nobinonly-0ubuntu4.

[John Vivirito (gnomefreak)]

William:
Can you please file a new bug using the command below:
ubuntu-bug firefox

Stegard:
Can you please do the same (running the command that i asked William to run)

Matt:
Can you please confirm that this bug is no longer happening after updates mentioned above

[Märt Suga (mart-suga)]

Trying to look fotki.com photos crashed my firefox many times in a row today. Unfortunately only error message is "Core dumped". Is there a better way to start firefox from bash to get more errors?

[Märt Suga (mart-suga)]

Well, this is getting really annoying. My firefox crashes about 5X every day now. This started again about a week ago.

[penalvch (penalvch)]

Original reporter = https://launchpad.net/~matt.eskes-deactivatedaccount

Matt Eskes, thank you for reporting this and helping make Ubuntu better. However, your crash report is missing. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. First, execute at a terminal:
cd /var/crash && sudo rm * ; sudo apt-get update && sudo apt-get -y upgrade && sudo apt-get -y install firefox-dbg && sudo service apport start force_start=1

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

Now reproduce the crash, then open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit.
If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'. If you run the command against the crash report and a window pops up asking you to report this, but then never opens a new report, you would be affected by https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921 . In order to WORKAROUND this, one would need to open the following file via a command line:
gksudo gedit /etc/apport/crashdb.conf

and comment out the line:
'problem_types': ['Bug', 'Package'],

by changing it to:
# 'problem_types': ['Bug', 'Package'],

Save, close, and try to file the crash report again via:
ubuntu-bug /var/crash/_my_crash_report.crash

Please follow https://wiki.ubuntu.com/MozillaTeam/Bugs when you file this crash report so the necessary information is provided.

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs