[app_server] crash in BRegion::_SetSize

[diver]

1. Ok I've found a way to reproduce it. Back trace sometime differs like in #3073, but anyway.
   
2. Start WonderBrush, the click Leaf menu and open Applications folder.
   
3. Now select all apps (alt+a) and drop them to the WonderBrush canvas.
   

This step will generate about 20 alert messages, close them.
Now if it didn't crashed repeat step 3 untill it will.

[diver]

If you try to drop on canvas /boot/beos/bin content and while error messages appearing start to switch workspaces it will crash much faster :-)
Oh, BTW, I'm using hrev28510 in VirtualBox.

[diver]

Another back trace with same steps

[diver]

I also get back trace like in #3073.

[anevilyak]

I can also relatively reliably reproduce this one while testing ticket #3195. If I very rapidly click to dismiss the read-only error dialogs, I hit the following backtrace every single time:

BRegion::_SetSize()
BRegion::operator= ()
RegionPool::GetRegion()
Window::SetFocus()
Desktop::SetFocusWindow()
Desktop::ActivateWindow()
Window::MouseDown()
MouseFilter::Filter()
EventDispatcher::_EventLoop()
EventDispatcher::_event_looper()
thread_entry()

I suspect there's a subtle race condition going on here, something like the window being set to the focus window right as it's being destroyed, or something along those lines.

[luroh]

Still seeing crashes in hrev28845 when rapidly dismissing the dialogs, although with a slightly different backtrace:

BRegion::_SetSize ()
BRegion::BRegion ()
BRegion::IntersectWith ()
Window::VisibleContentRegion ()
Window::GetEffectiveDrawingRegion ()
ServerWindow::_UpdateCurrentDrawingRegion ()
ServerWindow::_DispatchViewDrawingMessage ()
ServerWindow::_DispatchViewMessage ()
ServerWindow::_DispatchMessage ()
ServerWindow::_MessageLooper ()
MessageLooper::_message_thread ()
thread_entry ()

[umccullough]

Hit the same backtrace shown in the first image attached here using Haiku hrev29395

It's sitting in GDB now if there's anything that can be gathered further.

[stippi]

I think without having added some debugging or tracing output, at least I couldn't make much use of the GDB session. :-\

[umccullough]

Well, I'll reboot it when I get home tonight... Let me know if you think of anything before then (perhaps something spit out from KDL instead?)

In the event of an app_server crash like this, would ssh access to the box be helpful in any way? I suppose if there's nothing useful that can be retrieved from a gdb, session, perhaps it wouldn't help.

[stippi]

Maybe someone else could extract useful info. But I am not fluent with GDB at all. :-\

[diver]

This crash is not reproducible anymore. Feel free to close it.