Firefox seg faults on Extensions and Themes

Bug #19170 reported by Tom Bentley
8
Affects Status Importance Assigned to Milestone
firefox (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

I tried to update the web developer toolbar, and firefox crashed. Now, if I try
to bring up the Extensions or Themes windows, I can a seg fault.
"""
*** loading the extensions datasource
Segmentation fault
"""
is printed to stdout.

Revision history for this message
Tom Bentley (tom-bentley) wrote :

OK, it seems to be intermittant: The extensions window worked for my just now...
but Go > History seg faults too.

Revision history for this message
MichaelIhde (mike-ihde) wrote :

I just wanted to add that I experienced a similar problem after upgrading
firefox to 1.0.2-0ubuntu5.4. Prior to the update everything worked, after the
update anytime I closed a tab the browser would crash with a segmentation fault.
 By removing the Web Developer extension (version 0.9.3) the problem was fixed.
 If I reinstalled the web developer extension the problem returned. It is worth
noting that I have also set general.useragent.vendorSub to 1.0.4 so the
extension would install, this may be part of the problem.

Steps to reproduce the bug:
  1. Install firefox 1.0.2-0ubuntu5.4
  2. Set general.user.vendorSub to 1.0.4
  3. Instal web developer extension 0.9.3
(https://addons.mozilla.org/extensions/moreinfo.php?id=60)
  4. Restart firefox
  5. Open a new tab
  6. Close tab

At this point the browser will crash, and if run from the command line a
Segmentation Fault will result.

~Michael

Revision history for this message
Tom Bentley (tom-bentley) wrote :

> I just wanted to add that I experienced a similar problem after upgrading
> firefox to 1.0.2-0ubuntu5.4. Prior to the update everything worked, after the
> update anytime I closed a tab the browser would crash with a segmentation fault.

Yes, I should have mentioned that this has only started happening with
1.0.2-0ubuntu5.4

> It is worth
> noting that I have also set general.useragent.vendorSub to 1.0.4 so the
> extension would install, this may be part of the problem.

Again, I've also hacked my vendorSub to get around mozilla's annoying upgrade
policy.

Revision history for this message
Corey Burger (corey.burger) wrote :

This bug has been marked as a duplicate of bug 36208.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.