9055 - Mozilla GPFs on startup.

Status: VERIFIED DUPLICATE of bug 8830

(Core :: XPCOM, defect, P1)

Description

[Marcus Pallinger]

Mozilla nightly build (29-June-99) GPFs (General Protection fault) after asking
about the profiles.
This also appeared to happen under M7 (can't provide Talkback details as it
wouldn't conenct to server)

This is the same computer that bug 6165 was reported from. I'm not sure if this
is the same bug that is causing a GPF elsewhere or not. (FYI, M4 was the last
Milestone that I was able to run)

mozreg.dat was deleted before I unzipped the archive and ran it.
The contents of the text screen are included underneath the GPF info.

APPRUNNER caused an invalid page fault in
module XPCOM.DLL at 0137:1000fb4c.
Registers:
EAX=00000000 CS=0137 EIP=1000fb4c EFLGS=00010246
EBX=0075ef30 SS=013f ESP=0075ee48 EBP=0075ee70
ECX=00000001 DS=013f ESI=00000000 FS=2aaf
EDX=00000003 ES=013f EDI=1000f3cb GS=0000
Bytes at CS:EIP:
c6 46 02 78 e8 8b 3a 00 00 8b f8 59 c6 46 02 7c
Stack dump:
00000000 00000004 1000f3cb 0075ef2c 100120de 1000fb95 0075ee68 0075ef2c 10020220
00000000 0075ef40 1000faa6 0075eefc 80000000 03432ac5 0075eefc

*** Registering html library
width was not set
height was not set
Reading file...
Reading file...Done
Reading file...
Reading file...Done
Inside the Exit Wizard function...
DATA IS: ProfileName=mozProfile%ProfileDir=%
Created nsProfileCore
Entered Create Profile RoutineEntered Start AppRunner Routine
Run AppRunner with profile -> mozProfile <-
Created nsToolkitCore
JavaScript error: parent is not defined
URL: file:///C|/MARCUS/MOZILLA-990629-1358/BIN/res/profile/navigationFinish.xul
LineNo: 47

Reading file...
Reading file...Done

Comment 1

[Suresh Duddi (gone)]

Yuck we thought we had all our bases covered. This looks similar to bug # 8105 ,
the crash on startup thingy.

Comment 2

[Marcus Pallinger]

Yep, That's what I thoguht (I'm assuming you meant bug # 8150 ). It happened in
a nightly build that I downloaded
when I read the following message in the Project Status Pages (Dated June 11):
XPCOM 2.0
Submitted by Suresh Duddi <[e-mail]>
Suresh Duddi has this update regarding XPCOM:
Component Registry separated from the current global registry. It now exists in
    <exedir>/component.reg (unix and win)
    <exedir>/Component Registry (mac)
Files obsoleted by xpcom2.0 landing removed from the tree.

At that stage I wasn't testing the nightly builds regularly, so it may have been
happenign a while beforehand. I also can't rememebr when I actually read the
message...

I can't remember if this happened before or after the fix for
In other news, Talkback worked this morning on M7, so here's all tthe fun stuff:
Talkback ID: TB10598113Y (It has my Email address [e-mail]
attached)

The Text window said:
Talkback loaded Ok.
*** Registering html library
width was not set
height was not set
Loading  url resource:/res/profile/cpw.xul in WEbshell 8efa80
Reading file...
Reading file...Done
Reading file...
Reading file...Done
Loading  url
file://C:/MARCUS/MOZILLA-M7-FULLCIRCLE/X86REL/res/profile/content1.xul in
WEbshell 957470
Loading  url
file://C:/MARCUS/MOZILLA-M7-FULLCIRCLE/X86REL/res/profile/navigationStart.xul in
WEbshell 958100
Loading  url resource:/res/profile/content2.xul in WEbshell 957470
Loading  url resource:/res/profile/navigationFinish.xul in WEbshell 958100
Inside the Exit Wizard function...
DATA IS: ProfileName=mozProfile%ProfileDir=%
Created nsProfileCore
Entered Create Profile RoutineEntered Start AppRunner Routine
Run AppRunner with profile -> mozProfile <-
Created nsToolkitCore
Loading  url chrome://navigator/content/ in WEbshell 9a9140
Reading file...
Reading file...Done

APPRUNNER caused an invalid page fault in
module XPCOM.DLL at 0137:1000f949.
Registers:
EAX=00000000 CS=0137 EIP=1000f949 EFLGS=00010246
EBX=0076ef64 SS=013f ESP=0076ee7c EBP=0076eea4
ECX=00000001 DS=013f ESI=00000000 FS=0def
EDX=00000003 ES=013f EDI=1000f1f0 GS=0000
Bytes at CS:EIP:
c6 46 02 78 e8 5f 3a 00 00 8b f8 59 c6 46 02 7c
Stack dump:
00000000 00000004 1000f1f0 0076ef60 10011f41 1000f992 0076ee9c 0076ef60 1001f210
00000000 0076ef74 1000f8cb 0076ef30 80000000 039c26ad 0076ef30

As ususal if you want/need any more info, feel free to contact me.

Comment 3

[Suresh Duddi (gone)]

Marcus, could you try this the nightly jun 30 build. In a command shell:

set NSPR_LOG_MODULES nsComponentManager:5
set NSPR_LOG_FILE xpcoml.log
- change to the directory where apprunner.exe is
.\apprunner.exe

This should create xpcom.log in the current directory. Mail me the file after
you hit the crash.

If the instructions are hard to follow, I can make them simpler. This will give
me the xpcom's idea of why it crashed.

Thanks.

Marking bug P1 Critical.

Comment 4

[Marcus Pallinger]

Attachment: XPCOM Log File.

Comment 5

[Marcus Pallinger]

Here is the logfile of 30/06/99 nightly buuld after a crash.
Before i started, I deleted c:\windows\mozregistry.dat
removed the directory that mozilla was installed in
unzipped the new zip file
set the environment variables (Ps. MSDOS requires an = between the variable name
and the value, and the current directory is always in the path :)

ran apprunner.
Did the Profile Thing (accepted defaults)
then it crashed.

(Do you want me to keep on including what gets displayed in the text window and
the GPF message box?)

Hope this helps.

Comment 6

[Suresh Duddi (gone)]

Thank god you are windows wise Marcus. :-)

The print in the text window wont be required.

Comment 7

[Suresh Duddi (gone)]

After analyzing the logs, this aint the threading bug. I see multiple threads
hitting xpcom and the xpcom behaving properly.

So we need see what the stack trace looks like. I wouldn't be surprised if this
was the nsFileSpec crash on win95.

Marcus, we dont seem to be able to find the talkback incident you submitted.
Could you submit one again.

And thanks again for all the quick responses. It is a pleasure to work with you.

Comment 8

[chris hofmann]

assuming this is a dup of 8830 since the address of crash
is the same as other reports that point to
the crash that ends in
:\builds\seamonkey\mozilla\xpcom\io\nsFileSpec.cpp

see comment for incendent id=10399634

I can't load it at all. "APPRUNNER caused an invalid page fault in module
XPCOM.DLL at 0137:1000f949. Registers:
EAX=00000000 CS=0137
 EIP=1000f949 EFLGS=00010246 EBX=0076ef64 SS=013f ESP=0076ee7c EBP=0076eea4
ECX=00000001 DS=013f ESI=00000000
FS=0f9f EDX=00000003 ES=013f
 EDI=1000f1f0 GS=0000 Bytes at CS:EIP: c6 46 02 78 e8 5f 3a 00 00 8b f8 59 c6 46
02 7c Stack dump: 00000000 00000004 1000f1f0
0076ef60
 10011f41 1000f992 0076ee9c 0076ef60 1001f210 00000000 0076ef74 1000f8cb
0076ef30 80000000 035026ad 0076ef30 "

a few people are seeing this in m8 and it might be related
to attempts at loading IE favorites...

*** This bug has been marked as a duplicate of 8830 ***

Comment 9

[Marcus Pallinger]

Okay, Just so you can verify that it is the same bug, the Talkback incident
number is:
TB10652340E.
Thanks for your quick help too. Glad to have been working with you.
PS I'm on the CC list for #8830, so If it is the same bug, Feel free to ask me
to do some testing there, Otherwise, ask me via this bug if it's not :)

Comment 10

[Jay Patel [:jay]]

Verified Dup