527399 - Minefield/3.7a1pre (Gecko/20091108) crashes if FlashGot is installed.

Status: RESOLVED DUPLICATE of bug 527261

(Firefox :: Extension Compatibility, defect)

Description

[linuser]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.3a1pre) Gecko/20091108 Minefield/3.7a1pre
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.3a1pre) Gecko/20091108 Minefield/3.7a1pre

The latest Firefox nightly build (Mindfield) on linux platform ( Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.3a1pre) Gecko/20091108 Minefield/3.7a1pre ) crashes with a SIGSEV if the latest stable version of FlashGot is installed.

After updating my mindfield installation trhough the mozilla updater , it suddenly crashed at startup , while the previous builds (<= Gecko/20091107) all worked ... so I've created a new clean profile , I imported bookmarks , general preferences , and the latest saved tabs session , restarted the browser -> no crash.

Then I've began to install the extensions I have in the main profile . I've restarted the browser after installing every single extensions , in the following order :
- AdBlock Plus -> restart -> OK
- NoScript -> restart -> OK
- FlashGot -> restart -> Crash

I've came back on my original profile and started Mindfield in safe mode , disabled FlashGot and restarted the browser : no crash.

Finally I've created a new fresh profile , installed only the latest stable version of FlashGot , restarted the browser -> crash ; restarted again after submitting the first report -> crash

Reference to my reports :
- http://crash-stats.mozilla.com/report/index/983e6ba1-4d6a-4f09-82b8-531be2091108
- http://crash-stats.mozilla.com/report/index/8badb113-e77f-4791-9b32-acdc92091108 

Reproducible: Always

Steps to Reproduce:
1. create a new fresh profile
2. install the stable version of FlashGot
3. restart Mindfield
Actual Results:  
Crash with SIGSEV

Comment 1

[Jesper Hansen]

Adding flashgot author to CC, since this might be of interest to him

Comment 2

[philippe (part-time)]

That is probably the same as bug 527383 which was duped to bug 527261.

Comment 3

[Jesper Hansen]

Feel free to reopen if the patch applied in bug 527261 didn't work out in the next daily build.