604591 - Firefox crashed after showing the add-ons manager and the crash reporter didn't catch it

Status: RESOLVED INCOMPLETE

(Toolkit :: Add-ons Manager, defect)

Description

[Elferink]

User-Agent:       Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b6) Gecko/20100101 Firefox/4.0b6
Build Identifier: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b6) Gecko/20100101 Firefox/4.0b6

After a fresh install of Firefox 4 Beta 6, the add-on manager pops up.
When checking for newer versions of add-ons it gives a connection error message.
Wanting to report this I tried to install Test Pilot by going to the url (via https://testpilot.mozillalabs.com/faq and clicking Download Test Pilot) it gives the error:

The add-on could not be downloaded because of a connection failure on addons.mozilla.org

The host addons.mozilla.org is perfectly reachable.

Reproducible: Always

Steps to Reproduce:
1. go to url
2. click download button
Actual Results:  
error: The add-on could not be downloaded because of a connection failure on addons.mozilla.org

Expected Results:  
Install Pilot

Comment 1

[Henrik Skupin [:whimboo][⌚️UTC+2]]

Can you please set extensions.logging.enabled=true in about:config and check the error console after clicking the download button? Beside that you should probably also run a test with the latest nightly build, which you can find here: http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-mozilla-central/

Comment 2

[Elferink]

Attachment: screenshot of error

Comment 3

[Elferink]

Error console:

LOG addons.xpi: Download started for https://addons.mozilla.org/en-US/firefox/downloads/latest/13661?src=installservice to file C:\Users\ELFERI~1.TOP\AppData\Local\Temp\tmp-ny6.xpi
LOG addons.xpi: Download of https://addons.mozilla.org/en-US/firefox/downloads/latest/13661?src=installservice completed.
Warning: WARN addons.xpi: Download failed: TypeError: aChannel.securityInfo is null

Comment 4

[Elferink]

above was with 32 bit beta 6 then I downloaded:
firefox-4.0b8pre.en-US.win64-x86_64.installer.exe	13-Oct-2010 02:10
After installing it showed the add-on manager, which also had problems and after trying to load the default tabs it crashed (see screenshots)

Comment 5

[Elferink]

Attachment: add-on manager fail

Comment 6

[Elferink]

Attachment: Minefield crash

Comment 7

[Henrik Skupin [:whimboo][⌚️UTC+2]]

Those crashes are for the moment not related to this bug. You should file another one with all the details of the crash report sent. See http://support.mozilla.com/en-US/kb/Mozilla+Crash+Reporter

So are you able to install the mentioned add-on from comment 0 now?

Comment 8

[Elferink]

No it still cannot be installed and the weird thing is that at one time I had a feedback button on the toolbar (part of Test Pilot?) that has now again disappeared. 

The weird thing is also that if I used the feedback button or just used: http://input.mozilla.com/en-US/sad
It gives a CSRF error.

Forbidden (403)

CSRF verification failed. Request aborted.

I know this is another bug I don't know where to file that one.
I like Firefox but it feels like I am alpha testing over here :s

Comment 9

[Henrik Skupin [:whimboo][⌚️UTC+2]]

Ok, I can reproduce it now. It looks like that when loading this page we only request the file but never send out a version check, as what can be accomplished by clicking on "click here" on that page.

Comment 10

[Elferink]

(In reply to comment #7)
> Those crashes are for the moment not related to this bug. You should file
> another one with all the details of the crash report sent. See
> http://support.mozilla.com/en-US/kb/Mozilla+Crash+Reporter
> 
> So are you able to install the mentioned add-on from comment 0 now?

About the crash reporter, when minefield crashes there is no crashreporter.
The %APPDATA%\Mozilla\Firefox\Crash Reports\ directory does only contains 1 file modified today that is called InstallTime20100914083612 and contains the timestamp 1287129035
So right now I have gone back to 3.6

Comment 11

[Dave Townsend [:mossop]]

The failure to install Test Pilot is known bug 567699 and should be fixed by AMO soon. Is that the only remaining issue here?

Comment 12

[Elferink]

Well there is the minefield crash that the crash reporter can't handle.
Maybe this bug should be edited to represent that?

Comment 13

[Henrik Skupin [:whimboo][⌚️UTC+2]]

(In reply to comment #12)
> Well there is the minefield crash that the crash reporter can't handle.
> Maybe this bug should be edited to represent that?

That one could happen because you are using a 64bit build. I'm not really sure if the crash reporter work on Windows 64. You could try a 32bit build of Firefox.

Comment 14

[juan becerra [:juanb]]

Should this be blocking2.0?

Comment 15

[Dave Townsend [:mossop]]

If this bug is just about the uncaught crash then I don't think we can block on it till we understand what is happening.

Comment 16

[Elferink]

What do you want me to try?
32bit or ...?

Comment 17

[Dave Townsend [:mossop]]

Seeing if the crash happens in 32 bit would be helpful, also better steps to reproduce the crash

Comment 18

[Elferink]

Installed: firefox-4.0b8pre.en-US.win32.installer.exe
Same problem as attachment 483437 [details]
No crash!
"Test Pilot could not be installed because it is not compatible with minefield 4.0b8pre"

Looks ok, anything you need me to check?

Comment 19

[Henrik Skupin [:whimboo][⌚️UTC+2]]

Can you please open about:crashes, click the latest entry in the list and give us the link to the crash information page?

Comment 20

[Dave Townsend [:mossop]]

(In reply to comment #19)
> Can you please open about:crashes, click the latest entry in the list and give
> us the link to the crash information page?

Don't think that will be useful as the only case that crashed was 64-bit and didn't submit a crash report.

Comment 21

[Elferink]

about:crashes only shows reports from C:\Users\elferink.TOPICUS\AppData\Roaming\Mozilla\Firefox\Crash Reports doesn't it?
And as I said before there is nothing new there.
I still cannot start the 64bit version.
And about:crashes in 32bit shows only old crashes from 3.6

Comment 22

[Henrik Skupin [:whimboo][⌚️UTC+2]]

You can use WinDBG to catch the crash and get the useful information:
https://developer.mozilla.org/en/How_to_get_a_stacktrace_with_WinDbg

It would help us a lot! Thanks in advance.

Comment 23

[Elferink]

Attachment: debug log WinDbg

debug log WinDbg, WinDbg did not create a logfile so this is the console output (the same?)

Comment 24

[timeless]

The output is the same, yes. you'd need to use a path to which you can write, e.g. C:\Users\elferink.TOPICUS\firefox.log -- if you can figure out a way to explain that in the wiki page, please feel free to update it, perhaps we should add it to the faq section.

Please adjust c:\symbols to e.g. C:\Users\elferink.TOPICUS\symbols too for the same reason...

The log shows that it couldn't get symbols for minefield, which means one of the following:
* You're using a 64bit build - this seems likely as the paths are c:\program files and c:\windows\system32 and C:\Windows\WinSxS\amd64 instead of c:\program files (x86), c:\windows\system64 etc.
* You're using an hourly build instead of a nightly build

Anyway, we don't currently have 64bit symbols iiuc, so please grab a 32bit build.

Comment 25

[Dave Townsend [:mossop]]

(In reply to comment #24)
> Anyway, we don't currently have 64bit symbols iiuc, so please grab a 32bit
> build.

This doesn't help us, the problem is that he is seeing a crash in 64-bit but not 32-bit.

Comment 26

[timeless]

comment 0 was wow64...

anyway, we don't have symbols for 64bit builds atm, so unless someone has a try server build w/ symbols....

Comment 27

[Elferink]

ok, then I will wait for 64bit symbols
because as explained by Dave Townsend the problem is strictly with 64 bit.
Also I am using the following executable to produce the problem(as can be read in the comments):
http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-mozilla-central/firefox-4.0b8pre.en-US.win64-x86_64.installer.exe

Comment 28

[Matthias Versen [:Matti]]

Reporter: Is this till a problem with recent builds ?

Comment 29

[Elferink]

(In reply to Matthias Versen (Matti) from comment #28)
> Reporter: Is this till a problem with recent builds ?

I can not reproduce it, but between then and now I have reinstalled Windows at least once. So it's impossible to recreate the environment in which the bug occurred.

Comment 30

[Elferink]

(In reply to Elferink from comment #29)
> (In reply to Matthias Versen (Matti) from comment #28)
> > Reporter: Is this till a problem with recent builds ?
> 
> I can not reproduce it, but between then and now I have reinstalled Windows
> at least once. So it's impossible to recreate the environment in which the
> bug occurred.

*I can not reproduce it with the latest 64bit nightly.

Comment 31

[Blair McBride [:Unfocused] (UNAVAILABLE)]

Ok, thanks.

Looks like we can't make any more progress here then.