Opened 11 years ago

Last modified 19 months ago

#1718 assigned bug

malloc bugreport on Mozilla exit

Reported by: fyysik Owned by: nobody
Priority: normal Milestone: R1
Component: System Version: R1/pre-alpha1
Keywords: Cc: mattmadia@…
Blocked By: Blocking:
Has a Patch: no Platform: All

Description

When starting SeaMonkey from terminal and then exit app at some time, complaint from libroot appears in terminal: "seamonkey-bin: src/system/libroot/posix/malloc/superblock.h:194:void BPrivate::superblock::putBlock(BPrivate::block *): getNumAvailable() < getNumBlocks() ./run-mozilla.sh: line 424: 192 Kill Thread "$prog" ${1+"$@"}"

I wish to know what happens from libroot/malloc POV, this problem may happen in BeOS aswell, as Mozilla for BeOS exit code (and bootstrap code btw) is neither standard nor trivial.

Attachments (1)

syslog_when_seamonkey_exited_with_malloc_assertion.zip (16.8 KB) - added by fyysik 11 years ago.

Download all attachments as: .zip

Change History (7)

comment:1 Changed 11 years ago by bonefish

That's an assert() in the memory allocator, probably caused by a double free(), free()ing not allocated memory, or some memory corruption. Actually the failed assert() should call the debugger(), where you could at least see the back trace. Was anything printed in the serial debug output (respectively syslog)?

comment:2 Changed 11 years ago by axeld

The allocator likely has its own assert implementation that we might want to replace :)

comment:3 in reply to:  1 ; Changed 11 years ago by fyysik

Replying to bonefish:

where you could at least see the back trace. Was anything printed in the serial debug output (respectively syslog)?

Unfortunately my laptop lacks serial port (inspite there is "debug port" listed in BIOS - with resources which remind normal COM! very closely. That unfortunate Thinkpad R40e - very simplified model:(

comment:4 in reply to:  3 Changed 11 years ago by bonefish

Replying to axeld:

The allocator likely has its own assert implementation that we might want to replace :)

Unless I overlooked something, it doesn't. arch-specific.h includes <assert.h>.

Replying to fyysik:

Replying to bonefish:

where you could at least see the back trace. Was anything printed in the serial debug output (respectively syslog)?

Unfortunately my laptop lacks serial port (inspite there is "debug port" listed in BIOS - with resources which remind normal COM! very closely. That unfortunate Thinkpad R40e - very simplified model:(

As long as Haiku itself doesn't crash, you should have a syslog (/var/log/syslog). It is enabled by default.

comment:5 Changed 10 years ago by mmadia

Cc: mattmadia@… added

comment:6 Changed 19 months ago by axeld

Owner: changed from axeld to nobody
Status: newassigned
Note: See TracTickets for help on using tickets.