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
x/exp/shiny: panic is not panicky #13963
Comments
Darwin means I'm assigning this to crawshaw. |
With a similar panic inserted and
Which is not right, but is a little more information. @jnjackins do you get a stack trace if you send a SIGQUIT? |
Hi David. Thanks for having a look. I couldn't reproduce the issue the same way this time either, but I was able to reproduce it by inserting a panic into the handling of paint.Event in the tile example program:
And here is the stack trace I got by sending SIGQUIT:
I wonder if there is a deadlock occurring when the panic comes at an unlucky time, which would explain why it's difficult to reproduce consistently. |
go version devel +c5a2f36 Thu Jan 14 20:57:21 2016 +0000 darwin/amd64
Once a window has been initialized, any panics (either by calling panic() or some other means) do not exit the program or print a stack trace, but rather cause the program to hang. If the window has been published, the cursor becomes a spinning beachball.
cc @crawshaw @nigeltao
The text was updated successfully, but these errors were encountered: