#4350 closed bug (not reproducible)
App server heap corruption-related crashes
Reported by: | anevilyak | Owned by: | nobody |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Servers/app_server | Version: | R1/pre-alpha1 |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Description
On several different occasions in the past week or two I've encountered crashes that look something like the following:
#1: debugger() #2: __assert_fail() #3: BPrivate::hoardHeap:findAvailableSuperblock() #4: BPrivate::threadHeap::malloc() #5: malloc() #6; operator new() #7-#13 - various ops chaining off an std::map<long, BPrivate::BTokenSpace::token_info> insertion. #14: BPrivate::BTokenSpace::SetToken(this=0x18055f58, token=35, type=1, object=0x1861a048) #15: View::AttachedToWindow() #16: View::AddChild() #17: ServerWindow::_DispatchMessage() #18: ServerWindow::_MessageLooper() #19: MessageLooper::_message_thread() #20: thread_entry()
Pardon the lack of detail but alt+sysrq+d appears to be unusable from the gdb session used for app_server crashes. I've encountered this one while trying to reproduce #4343, and #698.
Change History (7)
comment:1 by , 15 years ago
comment:3 by , 15 years ago
Assertion in the same function reported in #4164. Doesn't contain any more helpful info either, though.
comment:4 by , 8 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:6 by , 5 years ago
Resolution: | → not reproducible |
---|---|
Status: | assigned → closed |
comment:7 by , 5 years ago
Milestone: | R1 |
---|
Remove milestone for tickets with status = closed and resolution != fixed
Note:
See TracTickets
for help on using tickets.
tried F12 by chance ? I think it's still mapped to it while in the app_server gdb session.