app_server exception, Call (abort() called)

[humdinger]

This is hrev53280, 32bit

Came back from dinner, was greeted by an app_server crash. I've seen this sort of crash a few times before. It may be related to the Otter browser that showed some rendering freezes before I went to dinner...

Part of the crash report (full report attached):

thread 569922: w:1483:offscreen 
state: Call (abort() called)

Frame		IP			Function Name
-----------------------------------------------
00000000	0x60bc3112	commpage_syscall + 0x2 
	Disassembly:
		commpage_syscall:
		0x60bc3110:             89e1  mov %esp, %ecx
		0x60bc3112:             0f34  sysenter  <--

0x7092ef98	0x1108655	debugger + 0x39 
0x7092efd8	0x117d6ae	abort + 0x52 
0x7092eff8	0x1103144	__terminate(void) + 0 
0x7092f020	0x110315f	__terminate(void) + 0x1b 
0x7092f1d0	0x1103b09	throw_helper(void) + 0x245 
0x7092f290	0x1103cd0	__throw(void) + 0x90 
0x7092f300	0x15152fc	DrawingEngine::FillEllipse(BRect, BGradient&) + 0x258 
0x70930a40	0x14ce6f6	ServerWindow::_DispatchViewDrawingMessage(int32, BPrivate::LinkReceiver&) + 0x1a86 
0x70930d70	0x14cc75d	ServerWindow::_DispatchViewMessage(int32, BPrivate::LinkReceiver&) + 0x38cd 
0x70930ea0	0x14c8d99	ServerWindow::_DispatchMessage(int32, BPrivate::LinkReceiver&) + 0x12c9 
0x70930f20	0x14d4902	ServerWindow::_MessageLooper() + 0x256 
0x70930f50	0x14a6e76	MessageLooper::_message_thread(void*) + 0x26 
0x70930f78	0x1110037	thread_entry + 0x27 
00000000	0x60bc3258	commpage_thread_exit + 0 

The syslog showed quite a few lines like these before the crash:

slab memory manager: created area 0xf7801000 (1235472)
slab memory manager: created area 0xf8001000 (1259938)
slab memory manager: created area 0xf8801000 (1283752)
slab memory manager: created area 0xf9001000 (1306406)
slab memory manager: created area 0xf9801000 (1330670)

[humdinger]

crash report

[waddlesplash]

Seen this anytime since?

[humdinger]

I don't think so.