-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
macOS: reliable crash on debugging #76
Comments
Finally produced a stack trace:
EDIT and a second one, in the audio callback: ==== C stack trace ===============================
Received signal 4 0001015be9b2 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
On macOS, Krom always crashes for me when started from inside Kode Studio and then quitting (i.e. Krom crashes when closing its window/closing the app).
I didn't manage to get a crash report/stack trace for this (though trying hard).
The reasons seems to be debugging. If I disable debugging by removing
'--debug', port.toString()
from the launch command line inKodeStudio.app/Contents/Resources/app/extensions/krom-debug/out/chromeDebugAdapter.js
, things work fine.Also, strangely, if I run with debug flags from the command line with some bogus port (e.g.
mykrom/macos/Krom.app/Contents/MacOS/Krom myproject/build/krom --debug 8080
), there's no crash on quitting Krom.The main annoyance with this is that macOS will ask on every new start of Krom, if you really want to launch it, as it crashed last time.
The text was updated successfully, but these errors were encountered: