143534 - Can't start Mozilla anymore out of the blue!

Status: RESOLVED WORKSFORME

(SeaMonkey :: General, defect)

Description

[TGOS]

From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows 98; QXW03354; Q312461)
BuildID:    2002050708

This build was always working fine so far and suddenly Mozilla crashed, don't 
know why. From this moment on I couldn't start it anymore, it crashes 
immediately. I did a reboot, but it still happens. It says an error takes place 
in necko.dll

Reproducible: Every time.
Steps to Reproduce:
1. I just open Mozilla, that's all.

Actual Results:  Mozilla craches during splash screen!

Expected Results:  Mozilla should start normally.

I used talkback. The talkback ID is TB6153798G

Comment 1

[Matthias Versen [:Matti]]

Reporter: 
Can you delete all files in your cache folder (in your user Profile) ?

Comment 2

[TGOS]

I deleted all files in the folder named 'Cache' in my profile directory, 
Mozilla still crashes during splash screen.

Comment 3

[Matthias Versen [:Matti]]

try this :
run "mozilla -profilemanager" and create an additional test profile.

Comment 4

[TGOS]

New profile works fine, old one still crashes.
How can Mozilla destory my profile? Any idea where the error is in the profile, 
so I can fix it without losing my profile?

Comment 5

[TGOS]

Okay, got it working again. I just had to remove the XUL.mfl file in my profile 
directory, which was 50% bigger than in the test profile. What's this file 
anyway? Mozilla seems to re-create it on every start-up. If there's any 
interest, I can post this file here.

Comment 6

[Matthias Versen [:Matti]]

-> wfm (corrupt profile)

Mozilla use a special language for his UI : XUL 
This file contains some XUL elements in a compiled format that mozilla doesn't
recompile it everytime... (AFAIK)

Comment 7

[TGOS]

Shouldn't there be some kind of protection against this error? E.g. shouldn't
the XUL.mfl loader detect that the file has been corrupted somehow (e.g. through
a crash of Mozilla) and then not use it on next start-up, but delete and rebuild
it, so that errors like this one can't take place anymore?