Closed Bug 10758 Opened 25 years ago Closed 25 years ago

Crash on shutdown with ShutdownXPCOM

Categories

(Core :: XPCOM, defect, P3)

Product:
Core
Component:
XPCOM
Platform:
Other
Linux
Type:
defect

Tracking

()

Status:
VERIFIED FIXED

People

(Reporter: dp, Assigned: ramiro)

Details

(Whiteboard: [19990809] waiting for good Linux build)

Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Target Milestone: M9
This is a code fix. If apprunner doesn't core dump on exit, this is fixed.
Whiteboard: [19990809] waiting for good Linux build
goodnews and badnews:
i tried build 1999-08-16-08-M9 and gdb said: 'Program exited normally.'

but with build 1999-08-23-08-M10, gdb had this to say:
Program received signal SIGSEGV, Segmentation fault.
0x404078f4 in CStartToken::IsEmpty ()

i couldn't get a stack trace for some reason.
i'll try again with the newest M10 build. when i finish downloading it...
(1999-08-23-15-M10)

beppe, you can qa assign this to me if you want...

platform: redhat linux 6.0, kernel 2.2.5 (GNOME/enlightenment)
Status: RESOLVED → REOPENED
QA Contact: beppe → phillip
Resolution: FIXED → ---
ok, i'm still getting a coredump.

1. start apprunner with gdb (mozillia-apprunner.sh -g -d gdb)
2. type run
3. when the start page is done loading on apprunner, select File|Exit
4. this is what you get:
Program received signal SIGSEGV, Segmentation fault.
0x40427848 in CCommentToken::CCommentToken ()
(gdb) bt
#0  0x40427848 in CCommentToken::CCommentToken ()
Cannot access memory at address 0x40427590.

i tried to get a stack trace with bt, but couldn't.

dp, is this an xpcom thing, or something else?
sorry, forgot to mention the platform info:
build 1999-08-27-05-M10, redhat 6.0 (GNOME/enlightenment)
Target Milestone: M9 → M10
Changing to M10 since M9 is already released.
Assignee: dp → rickg
Status: REOPENED → NEW
There are a lot of statics in the parser code. Rickg needs to figure out which
ones are xp and which ones aren't
Assignee: rickg → ramiro
Ramiro -- could this be related to the linking work you've been doing? If not,
please return it to me.
Rick,

I think the best thing would be to fix the usage of static objects in the
parser.
Status: NEW → RESOLVED
Closed: 25 years ago → 25 years ago
Resolution: --- → FIXED
I diabled XPCOM unloading dlls on shutdown. So this shouldn't core dump
anymore. This aint a fix. It is more of a workaround.

I am going to mark this bug fixed...
Status: RESOLVED → VERIFIED
verified
You need to log in before you can comment on or make changes to this bug.