@allenmonroesmith I'm not sure what this bug actually is yet, but it's happened twice in a row while using a debug build of the the new NS-scroller-free Bricksmith on Mojave with X-Code. The app shows as running but is unresponsive and is chewing up CPU; attempting to pause the app in the (already attached) debugger results in an X-Code error.
Given that it's happened twice now, I'll try a few sane things like comparing debugger to not debugger, running sample on it, checking resource usage, etc.
I don't know of any kind of bug in the sim that would cause "unresponsive to the debugger" as a symptom.
@allenmonroesmith I'm not sure what this bug actually is yet, but it's happened twice in a row while using a debug build of the the new NS-scroller-free Bricksmith on Mojave with X-Code. The app shows as running but is unresponsive and is chewing up CPU; attempting to pause the app in the (already attached) debugger results in an X-Code error.
Given that it's happened twice now, I'll try a few sane things like comparing debugger to not debugger, running sample on it, checking resource usage, etc.
I don't know of any kind of bug in the sim that would cause "unresponsive to the debugger" as a symptom.