[Lucid]NoScript crashes Firefox, crashes X-session

[Andreas Modinos]

Binary package hint: firefox

On Ubuntu 10.04 Beta 1 steps to repeat:

1. Install the NoScript extension
2. Restart Firefox
3. When the Ubuntu start-up page comes up, if you click on the NoScript icon in the lower right corner of the window it will cause a crash all the way back to GDM.

I've logged in and done this enough many times to know it repeats with absolute certainty.

What other factors affect this issue, I can only speculate.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: firefox 3.6+nobinonly-0ubuntu6
ProcVersionSignature: Ubuntu 2.6.32-18.27-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-18-generic i686
Architecture: i386
Date: Tue Mar 30 17:33:12 2010
FirefoxPackages:
 firefox 3.6+nobinonly-0ubuntu6
 firefox-gnome-support 3.6+nobinonly-0ubuntu6
 firefox-branding 3.6+nobinonly-0ubuntu6
 abroswer N/A
 abrowser-branding N/A
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100224.1)
ProcEnviron:
 LANG=fi_FI.utf8
 SHELL=/bin/bash
SourcePackage: firefox

[Pedro Villavicencio (pedro)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a ".crash" file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

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

If you are using Ubuntu with the Gnome desktop environment - launch nautilus and navigate to your /var/crash directory and double click on the crash report you wish to submit.
If you are using Kubuntu or Xubuntu you can file the crash using /usr/share/apport/apport-qt --crash-file=/var/crash/_my_crash_report.crash in a terminal - where _my_crash_report.crash is the crash you would like to report.

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. Thanks in advance for your cooperation and understanding.

[John Dawson (jfdawson)]

I experienced this bug with noscript also very repeatable.
Having removed noscript, the bug also occurred whilst trying to use the search box at the top right of the browser, so it may not be noscript specific. However I cannot repeat this reliably.

[Duane Bielling (hunkirdowne)]

Using Kubuntu LucidLynx Beta1 had exact problem as John Dawson with absolute repeatability of the noscript-induced crash and periodic crashing using the search window. As the beta progressed the search window crashes occurred less frequently. With the release of Beta2 no search window crashes have occurred yet. Noscript crashes occur often but not every time.

Furthermore, running "/usr/share/apport/apport-kde --crash-file=/var/crash/_usr_lib_firefox-3.6.3_firefox-bin.1000.crash" in a terminal produces an out of memory error message in a popup: "Sorry, the program "firefox-bin" closed unexpectedly <line break> Your computer does not have enough free memory to automatically analyze the problem and send a report to the developers."

There is information that may be useful from the .xsession-errors file. I copied the file before and after and saved the differences in a new file (see attached "dbg.firefox.xession-errors.post-crash-differences").

[tm-o (tm-o)]

I seem to have this same problem. I have Radeon M6 GPU and found this bug report: https://bugs.freedesktop.org/show_bug.cgi?id=27510

[hgergo (hutongergo)]

i have the same bug wit no skript and when i am wisiting ebay

[Andreas Modinos (blueturtl)]

After the affected package was changed, how do I submit relevant info? Apport-collect just said no data was collected.

[Duane Bielling (hunkirdowne)]

A bit more testing. This seems independent of Desktop Environment (affects Xubuntu as well as Kubuntu) and graphics card (both ATI and nVidia tested positive). Furthermore have an issue without NoScript even installed where using the search bar can crash Xorg. Bottom line, while there may be faulty code in Mozilla Firefox causing the application to crash, IMO there still exists a burden on the part of Xorg to not crash when the application crashes. Just an opinion -- I'm not a developer just a user.

My system is not mission critical but this issue is severe enough to give one pause prior to installing this operating system in a mission critical environment if it is not resolved prior to release.

[Duane Bielling (hunkirdowne)]

More information: I believe this to be an issue with Firefox Add-Ons in general as I have repeated issues using NoScript and just recently with Cookie Monster (with NoScript disabled).

[Robert Hooker (sarvatt)]

Unfortunately we need some info here to see what the problem is.. If apport-collect 551754 will not add the logs can you file a new bug with the command ubuntu-bug xorg and mark it as a duplicate to this one? Please do it right after reproducing this issue so the information is in the logs that will be attached.

[Robert Hooker (sarvatt)]

Actually, no need. Given the above linked bug report I can see that this is a duplicate of another bug which has a fix available that we hope to pick up soon.