Closed Bug 5896 Opened 26 years ago Closed 25 years ago

Apprunner crash on close

Categories

(Core Graveyard :: Tracking, defect, P2)

x86
Windows 98
defect

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 7799

People

(Reporter: basic, Assigned: don)

Details

Build 1999050308

run apprunner
wait for apprunner to load
close apprunner using the [x] button
This message appears:

APPRUNNER caused an invalid page fault in
module KERNEL32.DLL at 015f:bff7b997.
Registers:
EAX=00000000 CS=015f EIP=bff7b997 EFLGS=00000246
EBX=00000008 SS=0167 ESP=00daff28 EBP=00daff38
ECX=7802df7a DS=0167 ESI=78034120 FS=3b97
EDX=bffc9490 ES=0167 EDI=815bd920 GS=0000
Bytes at CS:EIP:
ff 76 04 e8 26 89 ff ff 5e c2 04 00 56 8b 74 24
Stack dump:
78034048 78001020 78034120 061b1d70 00daff98 78002b70 0000000d 78003a07
815bd920 7800ba71 000000ff 00000001 00000000 7800bcfe 000000ff 0000002b

3 times

and this is found in the dos box.

Setting Back menuitem to enabled
Document file:///C|/UTILITIES/MOZILLA-WIN32/BIN/res/samples/BrowserInitPage.html
 loaded successfully
Init!
Reading file...
Reading file...Done
adding "resource:/res/rdf/remote-flash-1.rdf" to the tree
Reading file...
Reading file...Done
adding "resource:/res/rdf/remote-flash-2.rdf" to the tree
Reading file...
Reading file...Done
adding "resource:/res/rdf/remote-flash-3.rdf" to the tree
Reading file...
Reading file...Done

runtime error R6016
- not enough space for thread data

runtime error R6016
- not enough space for thread data

runtime error R6016
- not enough space for thread data

I don't know if this could be related to bug #5164
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → WORKSFORME
Hmmmm ... I can't make this happen with today's build.  Are you trying to close
the window before it's completely rendered?
No, I waited until apprunner had fully loaded before trying to close it.
I wonder if it could be because of some other software I have on my system like
IE5 and related accessories?
Status: RESOLVED → REOPENED
This bug also cause other applications to crash or close without a warning! I'm
pretty sure it is caused by memory leaks.

Fullcircle in M5 can't detect the crash caused by this bug.

Just searched through news.mozilla.org and found this message entitled "leak
status report":
http://www.dejanews.com/[ST_rn=ps]/getdoc.xp?AN=474369212

Could this be related?
One more note:

In the DOS box I see this:

Reading file...
Reading file...Done
adding "resource:/res/rdf/remote-flash-1.rdf" to the tree
Reading file...
Reading file...Done
adding "resource:/res/rdf/remote-flash-2.rdf" to the tree
Reading file...
Reading file...Done
adding "resource:/res/rdf/remote-flash-3.rdf" to the tree
Reading file...
Reading file...Done

runtime error R6016
- not enough space for thread data

runtime error R6016
- not enough space for thread data

runtime error R6016
- not enough space for thread data

and when it crashes I get 3 error messages!

Is there a relation?
Assignee: don → law
Status: REOPENED → NEW
Priority: P3 → P2
Target Milestone: M6
Bill, can you make this happen?
Guys, I just thought I'd report that apprunner crashes for me on close, too.
Here, I get a segfault when running it under i386 Red Hat 6.0 and the CVS source
for Mozilla.  Build ID: 1999043018.  Funny thing is, it does not happen
everytime though.  I think it mainly happens after I've viewed many websites.
If you guys could tell me how to configure the Mozilla build process to build
Mozilla so it will do a core dump with all the necessary debugging symbols, I
will send you the core dump so you guys can debug it more thoroughly.  Just say
the word.
QA Contact: 3853 → 3849
Resolution: WORKSFORME → ---
Updating QA Contact
Status: NEW → ASSIGNED
To build with debugging symbols, just set MOZ_DEBUG=1 in your shell before
kicking off the build.  Of course, that's spoken the way a windows weenie would
say it; if it doesn't translate, let me know.
Assignee: law → don
Status: ASSIGNED → NEW
Target Milestone: M6 → M9
I'm moving this out a few milstones until we can get a reproducible case in
house.
Status: NEW → RESOLVED
Closed: 26 years ago25 years ago
Resolution: --- → DUPLICATE
Status: RESOLVED → VERIFIED
Moving all Crash on Exit bugs to 7799

*** This bug has been marked as a duplicate of 7799 ***
Moving all Apprunner bugs past and present to Other component temporarily whilst
don and I set correct component.  Apprunner component will be deleted/retired
shortly.
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.