On Wed, 19 Dec 2018 at 17:46, Ben Hekster <ben.heks...@foghorn.io> wrote: > Stack trace of crashing thread:
Thank you. > 21 AppKit 0x00007fff3280e99e -[NSWindow > setFrame:display:] + 51 > 22 AppKit 0x00007fff3281932f -[NSWindow > setFrame:display:animate:] + 130 > 23 qemu-system-arm 0x00000001035cb13a -[QemuCocoaView > switchSurface:] + 2282 > 24 qemu-system-arm 0x00000001035d102e cocoa_switch + 94 > 25 qemu-system-arm 0x00000001035bfa46 > dpy_gfx_replace_surface + 278 > 26 qemu-system-arm 0x00000001035c1721 > qemu_console_resize + 209 > 27 qemu-system-arm 0x000000010310be80 > bcm2835_fb_reconfigure + 112 OK, so this is what I suspected we might be doing -- certain functions called from device emulation (so on the CPU thread) end up calling in to the cocoa UI DisplayChangeListenerOps callbacks, which at the moment are written to directly call OSX functions. But only certain guest behaviour (in this instance a guest resizing the display) causes this, so a lot of guest use cases will work OK even on Mojave. > probably a manifestation of https://bugs.launchpad.net/qemu/+bug/1802684 Yep. If you could test the patchset at http://patchew.org/QEMU/20181201123056.432-1-peter.mayd...@linaro.org/ and confirm that it fixes the problem that would be great. thanks -- PMM
