27535 - Registry corruption on Win98

Status: VERIFIED FIXED

(Core :: XPCOM, defect, P1)

Description

[David Hyatt]

On my Win98 machine at home, I cannot run more than 3-4 times before a profile 
becomes corrupted and unusable.  I always get the following stack crash when I 
try to start.

I have deleted my registry and removed all traces of Mozilla and started with a 
fresh MOzilla.  This always ends up happening.

KERNEL32! bff768a4()
nr_ReadData(_regfile * 0x02d7c8c0, _desc * 0x0097ea90, unsigned long 512, char * 
0x004bf620 gCurstr) line 908 + 44 bytes
NR_RegGetEntryString(void * 0x02d7bdd0, long 10159, char * 0x004bf110, char * 
0x004bf620 gCurstr, unsigned long 512) line 2861 + 21 bytes
vr_SetCurrentNav(char * 0x004bf0f4, char * 0x00d2e9b0, char * 0x00000000) line 
512 + 30 bytes
vr_Init() line 194 + 19 bytes
VR_ValidateComponent(char * 0x02d7c990) line 986 + 5 bytes
nsXPINotifierImpl::IsNewerOrUninstalled(const char * 0x02d7c990, const char * 
0x02d78120) line 318 + 9 bytes
nsXPINotifierImpl::OnEndLoad(nsXPINotifierImpl * const 0x02d70830, nsIRDFXMLSink 
* 0x02d72b78) line 596 + 58 bytes
RDFXMLDataSourceImpl::EndLoad(RDFXMLDataSourceImpl * const 0x02d72b78) line 993
RDFContentSinkImpl::DidBuildModel(RDFContentSinkImpl * const 0x02d72f40, int 1) 
line 481 + 23 bytes
CWellFormedDTD::DidBuildModel(CWellFormedDTD * const 0x02d794b0, unsigned int 0, 
int 1, nsIParser * 0x02d71400, nsIContentSink * 0x02d72f40) line 291 + 20 bytes
nsParser::DidBuildModel(unsigned int 0) line 592 + 55 bytes
nsParser::ResumeParse(nsIDTD * 0x00000000, int 1) line 1022
nsParser::OnStopRequest(nsParser * const 0x02d71404, nsIChannel * 0x02d73bb0, 
nsISupports * 0x00000000, unsigned int 0, const unsigned short * 0x00000000) 
line 1413 + 19 bytes
RDFXMLDataSourceImpl::OnStopRequest(RDFXMLDataSourceImpl * const 0x02d72b80, 
nsIChannel * 0x02d73bb0, nsISupports * 0x00000000, unsigned int 0, const 
unsigned short * 0x00000000) line 1073 + 42 bytes
nsResChannel::OnStopRequest(nsResChannel * const 0x02d73bb4, nsIChannel * 
0x02d73970, nsISupports * 0x00000000, unsigned int 0, const unsigned short * 
0x00000000) line 596 + 53 bytes
nsFileChannel::OnStopRequest(nsFileChannel * const 0x02d73974, nsIChannel * 
0x02d73740, nsISupports * 0x00000000, unsigned int 0, const unsigned short * 
0x00000000) line 446 + 45 bytes
nsOnStopRequestEvent::HandleEvent(nsOnStopRequestEvent * const 0x02d78420) line 
279
nsStreamListenerEvent::HandlePLEvent(PLEvent * 0x02d78360) line 93 + 12 bytes
PL_HandleEvent(PLEvent * 0x02d78360) line 526 + 10 bytes
PL_ProcessPendingEvents(PLEventQueue * 0x00d34340) line 487 + 9 bytes
_md_EventReceiverProc(HWND__ * 0x00000b4c, unsigned int 53502, unsigned int 0, 
long 13845312) line 975 + 9 bytes
KERNEL32! bff7363b()
KERNEL32! bff942e7()
00978b8a()

Comment 1

[David Hyatt]

Nominating as beta1.  Mozilla is unusable on my Win98 machine at home.

Comment 2

[David Hyatt]

cc'ing dveditz.  This may be more his territory?

Comment 3

[David Hyatt]

Note that the profile manager comes up fine.  This happens after I select a 
profile, implying that a specific profile becomes corrupted.

Comment 4

[David Hyatt]

It gets worse.  I cannot even migrate my existing 4.x profile.  Right after the 
migration completes, I get the same crash.

I'm unable to even use the product on my machine.  Upgrading severity and 
priority.

Comment 5

[Daniel Veditz [:dveditz]]

Is the stack trace always the same? The only thing using the VR_ APIs at 
startup would be the xpi notification thingy. And it's looking at the old 4.x 
version registry (nsreg.dat) not the mozilla profile registry.

Try removing the xpiflash.dll component and see if the crash goes away. That 
will either exonerate or implicate the notification code as the intermediate 
culprit. Intermediate because the real problem may well be corruption in your 
4.x version registry.

Comment 6

[David Hyatt]

Yes, the problem goes away when I delete xpiflash.dll.  Interesting.  Whatever 
corruption may be in my 4.x registry doesn't seem to be harmful in 4.x....

Comment 7

[Doug Turner (:dougt)]

david, could you try going to:

ftp://sweetlou/products/client/seamonkey/windows/32bit/x86/current/update.html

and doing an update of one or more components?  do you see the same crash?

Comment 8

[leger]

Putting on the PDT+ radar for beta1.

Comment 9

[David Hyatt]

Dunno if it matters or not.  The assertion is that my 4.x registry is corrupted.

Comment 10

[Daniel Veditz [:dveditz]]

Starting a few minutes ago the 4.x registry is no longer used by the XPInstall 
notification feature. The profile manager still grovels there for old profiles 
but that's not where you're crashing.

This sidesteps the problem: we don't know why your registry was corrupted. 
Could you mail it to me? (windir\nsreg.dat)

This is probably not dp's bug in any case. Changing component, but will let dp 
reassign if he wants.

Comment 11

[Suresh Duddi (gone)]

Hyatt, did you have to delete dist/bin/component.reg If not, this aint a 
component registry bug. Doesn't look like it is as hyatt probably doesn't know 
this even exists.

So I would be the wrong owner. Dan do you think I might add value to this bug 
in any way ? Please let me know and reassign. I will do my best.

Comment 12

[Daniel Veditz [:dveditz]]

We're not using that registry anymore. Please let me know if this continues to 
happen.

Comment 13

[leger]

Adding verifyme keyword.

Comment 14

[leger]

This seesm to be ok now.  Marking Verified.  hyatt, please reopen if you 
disagree.