Skip to content
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.

Sign up for GitHub

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

Jump to bottom

x/exp/shiny: darwin signal handling SIGSEGV #13895

Closed
jnjackins opened this issue Jan 10, 2016 · 4 comments
Closed

x/exp/shiny: darwin signal handling SIGSEGV #13895

jnjackins opened this issue Jan 10, 2016 · 4 comments
Labels
FrozenDueToAge

Comments

@jnjackins
Copy link
Contributor

go version devel +57b1e55 Sat Jan 9 03:30:40 2016 +0000 darwin/amd64

I'm building a graphical program using x/exp/shiny, and recently I started getting this error whenever a mouse event is generated:

Segmentation fault: 11

I'm on a Mac, and using the "report to apple" dialogue that pops up, I also get the following (full output attached):

...
Crashed Thread:        0  Dispatch queue: com.apple.main-thread
Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_PROTECTION_FAILURE at 0x00007fff5f3ffff8
...
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   edit                            0x0000000004040a25 runtime.sighandler + 725 (signal_amd64x.go:129)
...

I'm not sure if this is a bug in the darwin code for shiny, a new bug introduced with the recent changes to signal handling, or an older bug that I've somehow tickled.

I can reproduce this consistently by running e.g. golang.org/x/exp/shiny/example/tile, and clicking. The error message varies between "signal: segmentation fault" and "Segmentation fault: 11".

Running with -race does not report any data races.

full crash report
@bradfitz
Copy link
Contributor

/cc @nigeltao @crawshaw @ianlancetaylor

@bradfitz bradfitz changed the title darwin signal handling SIGSEGV x/exp/shiny: darwin signal handling SIGSEGV Jan 10, 2016
@jnjackins
Copy link
Contributor Author

The crash was introduced by this commit: golang/exp@bb37e7d (found using git bisect). I can also reproduce the crashes with older versions of Go, so I think the bug probably lies somewhere in that change.

@jnjackins
Copy link
Contributor Author

I mailed https://go-review.googlesource.com/#/c/18424/.

@gopherbot
Copy link

CL https://golang.org/cl/18424 mentions this issue.

@golang golang locked and limited conversation to collaborators Jan 13, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
FrozenDueToAge
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@bradfitz @jnjackins @gopherbot