332428 - Crash on startup which was fixed only by reinstalling firefox

Status: RESOLVED WORKSFORME

(Firefox :: General, defect)

Description

[Vasya Pupkin]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1

Today firefox crashed after visiting some page. I god Talkback Agent popped up. I filled form and pressed 'Send' button. Report couldn't be sent because talkback.mozilla.org is not responding. I minimized talkback window and started firefox again. Loaded one page and it crashed again. I filled one more talkback report and pressed 'Send'. After that firefox begun to crash on startup. Even talkback agent stopped to appear. I tried to run it in safe mode but it crashed even in this case. I tried to run another profile which couldn't be corrupted, but no luck again. Then I uninstalled firefox and installed it again. This fixed the problem. I have 2 drwtsn32 logs with crash information.

http://home.shad.pp.ru/tmp/ff-crash-drwtsn32.log
http://home.shad.pp.ru/tmp/ff-safemode-crash-drwtsn32.log

Reproducible: Didn't try

Steps to Reproduce:

Comment 1

[Nickolay_Ponomarev]

Attachment: drwatson report

As far as I understand this is the relevant stack, don't know if it's confused or not. Did you delete the contents of the program folder? I wonder if this could be caused by corrupted JS components or something..

!js_FinishCodeGenerator 
!js_FinishCodeGenerator 
!js_FinishCodeGenerator 
!js_FinishCodeGenerator 
!js_FinishCodeGenerator 
!js_FinishCodeGenerator 
!js_FinishCodeGenerator 
!js_FinishCodeGenerator 
!js_CompileTokenStream 
!js_CompileTokenStream 
!JS_CompileUCScriptForPrincipals 
!JS_CompileFileHandleForPrincipals 
!NS_RegistryGetFactory 
!NS_RegistryGetFactory 
!NS_RegistryGetFactory 
!NS_RegistryGetFactory 
!NS_RegistryGetFactory 
!NS_RegistryGetFactory 
!nsCreateInstanceFromCategory::operator() 
!nsCreateInstanceFromCategory::operator() 
!NS_InitXPCOM3_P 
!<nosymbols> 
!<nosymbols> 
!<nosymbols> 
kernel32!ProcessIdToSessionId

Comment 2

[Brendan Eich [:brendan]]

asqueela: Don't blame based only on the top of stack frames.  There's no known JS bug of this kind, and it's hard to envision how another crash would trigger this crash, unless the profile were corrupted.  But comment 0 said that trying another profile didn't help.

This smells like memory corruption, or possibly even code corruption if only reinstalling Firefox fixes things.

/be

Comment 3

[Brendan Eich [:brendan]]

Reporter: can you list your installed plugins, and anything else that might have been common between profiles, but reset or overwritten by reinstalling Firefox?

/be

Comment 4

[Nickolay_Ponomarev]

I don't normally blame based just on the top of the stack, but I guessed the JS components in the *program* folder got corrupted. I understand this is not very likely, but it's the best explanation I could think of.

Comment 5

[Brendan Eich [:brendan]]

If some bit error corrupted code in js3250.dll, the bug should be filed with the disk vendor -- not much we can do about it.

I suspect something deeper, and more our fault, went wrong.  Just a hunch.  But worth keeping this bug around for a while longer, and in a general component in Firefox so it can attract dups.

/be

Comment 6

[Nickolay_Ponomarev]

I meant the *.js component files. Not much can be done about that either, but at least spidermonkey shouldn't crash when compiling them (assuming it was the reason). Anyways this was just my guess.
(Do you keep resetting branch to 1.0 intentionally?)

Comment 7

[Brendan Eich [:brendan]]

Again we don't know of any way for bad JavaScript source to cause such a crash, but there could be a new bug here.  If so, it would be good to recover all the .js and .jar files from the bad installation.

The symbolic stack trace is not right, but that could be a talkback server prob.

/be

Comment 8

[Brendan Eich [:brendan]]

And no, I don't mean to reset the Version.

/be

Comment 9

[Vasya Pupkin]

I didn't modyfy *anything* in program folder. I happend on it's own. Never happened before and doen't happen after reinstalling. I didn't even modify profiles, they all working as before, after reinstalling of firefox. I don't have a clue what could cause this.. :(

Comment 10

[timeless]

Comment on attachment 216933 [details]
drwatson report

drwatson is at the mercy of the symbols it has available. talkback builds are stripped, the symbols are left with the talkback server. this means drwatson can't give useful stacks. and it means people shouldn't post drwatson reports for normal builds. doing so results in people wasting time getting very confused.

Comment 11

[Vasya Pupkin]

(In reply to comment #10)
Sorry.
But what's up with the talkback server? I can't send reports for 2 days already.

Comment 12

[Nickolay_Ponomarev]

Not sure what is happening with it now, but it almost never worked for me. 
Do you still have the old program files (from Program Files\Mozilla Firefox by default)? I think it would be interesting to know the difference between the old and new working files.

Comment 13

[Vasya Pupkin]

(In reply to comment #12)
Nope, I didn't keep them.

Comment 14

[Jay Patel [:jay]]

Vasya:  We had some Talkback server issues the past week, but things are back up and running ok.  Try submitting your crash now and let me know if it goes through.  Thanks.

Comment 15

[Wayne Mery (:wsmwk)]

reporter, Do you still see this problem. If you do not, please close the bug with resolution WORKSFORME, INVALID, etc as may be appropriate to your situation (but not FIXED unless you know the bug with the patch). 

If you still see problem using a current version of Firefox or trunk build, please provide additional detail.

Comment 16

[Mats Palmgren (inactive)]

Please try Firefox 3:  http://www.mozilla.com/firefox/
File a new bug if the problem remains.  Thanks for your report.

-> WORKSFORME