Opened 16 years ago
Closed 15 years ago
#3568 closed bug (duplicate)
Crash in BeZilla thread exit notification
Reported by: | stippi | Owned by: | axeld |
---|---|---|---|
Priority: | normal | Milestone: | R1 |
Component: | - General | Version: | R1/pre-alpha1 |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Description
[Switching to team /boot/apps/BeZillaBrowser/BeZillaBrowser (229) thread moz-thread (74939)] 0x01a461eb in BPrivate::processHeap::free () from /boot/beos/system/lib/gcc2/libroot.so (gdb) bt #0 0x01a461eb in BPrivate::processHeap::free () from /boot/beos/system/lib/gcc2/libroot.so #1 0x01a47ad9 in free () from /boot/beos/system/lib/gcc2/libroot.so #2 0x0177a408 in sv_close () from /boot/beos/system/lib/gcc2/libnetwork.so #3 0x0177acac in gen_close () from /boot/beos/system/lib/gcc2/libnetwork.so #4 0x017862fd in __net_data_destroy () from /boot/beos/system/lib/gcc2/libnetwork.so #5 0x01a37e12 in _thread_do_exit_notification () from /boot/beos/system/lib/gcc2/libroot.so #6 0x01a37c3f in thread_entry () from /boot/beos/system/lib/gcc2/libroot.so #7 0x70512fec in ?? () (gdb)
Happened while browsing. Revision is hrev29533. GCC 4 image with GCC 2 compatibility libs.
Change History (2)
comment:1 by , 16 years ago
comment:2 by , 15 years ago
Resolution: | → duplicate |
---|---|
Status: | new → closed |
This should be a dup of #4949 (already fixed).
Note:
See TracTickets
for help on using tickets.
Unfortunately you cut the line with the "crashing" event. Would be interesting to know whether this was an assert. Which would make a memory corruption/double free on Bezilla's part the most likely cause.