434159 - Extension Manager crashes when initially used

Status: RESOLVED DUPLICATE of bug 431065

(Toolkit :: Add-ons Manager, defect)

Description

[Hugo]

User-Agent:       Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; SLCC1; .NET CLR 2.0.50727; Media Center PC 5.0; .NET CLR 3.0.04506)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9) Gecko/2008051206 Firefox/3.0

When I first started FF3rc1, none of my extentions from FF2 appeared to be working. Opened "Add-ons" -> "Extentions" and all my previous extentions were listed correctly. Clicked on "Find Updates" and none were available, however, suddenly most of my extentions were marked as incompatible with FF3rc1. Still the ones marked as being okay did not seem to be working. I clicked on one of the compatible extentions then its "Options" botton and nothing happened. When I clicked on another button, I discovered the Add-on Manager had frozen and nothing worked. The only way to close the manager was with Windows Task Manager.

I then proceeded to click on the "Options" button for each extention which FF indicated as working and each time the manager froze and each time I had to end the task and relaunch FF. Fortunately only six of my 25 extentions were indicated as being compatible with FF3rc1, so I didn't have to go through this cumbersome testing too long!

I then went to the "Add-ons" website and re-installed the six compatible extentions. I retested the "Options" on each one and the manager continued to freeze each time. Suddenly, on one of my relaunches of FF, in addition to my homepage opening, the "About Download Statusbar" page also opened (chrome://downbar/content/aboutdownbar.xul)[Download Statusbar being one of my extentions indicated as being compatible with FF3rc1] From this point onward the "Options" button for Download Statusbar in the FF Extention Manager also worked.

I then re-tested the "Options Buttons" for the other extentions. During this process, the manager continued to freeze and I would have to go thru the "end task" and relaunch FF as described before. However, a new bug developed. Each time I launched FF, the "About Download Statusbar" page also continued relaunching. This happen even if I just closed FF normally (without first making the Extention Manager freeze). After about nine relaunches of FF, the "About D. S." page suddenly stopped launching and hasn't launched since.

Also, gradually, several of the other Extention's "Options" buttons started working properly. As each Extention's "options" button started working, the Extention would also begin operating properly during web browsing sessions. To date, Download Statusbar, Flagfox, Flashblock, and McAfee Site Advisor are all working okay. Adblock Plus and Speed Dial are not working properly. Clicking on the "Options" button for these two extentions continues to freeze the Extention Manager and they don't seem to be working at all (i.e. during browsing). One note, although clicking on the "Options" button causes the manager to freeze,  the "Disable" button works properly. 

Reproducible: Sometimes

Steps to Reproduce:
1.SEE ABOVE DETAILS
2.
3.
Actual Results:  
SEE ABOVE DETAILS


Expected Results:  
SEE ABOVE DETAILS

SEE ABOVE DETAILS

Comment 1

[Dave Townsend [:mossop]]

Please attach copies of extensions.cache, extensions.rdf, extensions.ini and extensions.log to this bug report. They are located in your profile folder

http://support.mozilla.com/en-US/kb/Profiles

Comment 2

[Hugo]

Attachment: extensions.cache

per Dave Townsend's request -- comment #1

Comment 3

[Hugo]

Attachment: extensions.rdf

Per dave Townsend's request -- comment #1

Comment 4

[Hugo]

Attachment: extensions.log

Comment 5

[Hugo]

Attachment: extensions.ini

Comment 6

[Hugo]

Attachment: extensions-1.ini

per Dave Townsend's request -- comment #1

Comment 7

[Dave Townsend [:mossop]]

Ok what is happening here is that the extension manager is unable to overwrite the extensions.ini file in your profile, hence why it created an extensions-1.ini file that normally wouldn't exist. This would most commonly happen if for some reason the extensions.ini file was marked read only or there was a disk problem. If you can delete the extensions.ini file the issue should resolve itself, but you may want to run a disk check just in case there are hidden problems there.

Comment 8

[Dave Townsend [:mossop]]

Did what I suggested fix the issue? Did a disk check find any problems? Are you using any anti-virus or anti-malware tools?

Comment 9

[Dave Townsend [:mossop]]

And do you happen to have TortoiseSVN installed?