-
Notifications
You must be signed in to change notification settings - Fork 20
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
SIGSEGV with a signal containing *glib.Value
#55
Comments
The example gtk4/simple crashes with this message. Any known workaround? |
What commit are you on? It shouldn't crash on |
Upgraded but still crashing: Trace (using go 1.18 from Arch official repos): runtime stack: goroutine 1 [syscall]: |
This looks to be a completely different bug. Can you run it in gdb and show me the stack trace of the thread? |
Yes, it seems the error is different after the upgrade. The GTK4 demos run properly. (gdb) run Thread 1 "simple" received signal SIGSEGV, Segmentation fault. |
I'm actually not sure why this happens. Can you rebuild using If that doesn't work, does running it with |
Also, it would be better if you could make a new issue for this problem. |
GSK_RENDERER=cairo did the trick. Thanks and sorry for polluting you issue. |
Stack trace:
Possible cause:
The text was updated successfully, but these errors were encountered: