-
Notifications
You must be signed in to change notification settings - Fork 18k
syscall: win.GetMessage syscall.Syscall6 crash #41284
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
Comments
goroutine 54 [syscall, locked to thread]: |
This kind of crash will happen if you pass bad arguments, such as invalid pointers, to the Windows system call. There's no particular reason to think that it is a problem with Go. Different versions of Windows act differently. If you are convinced that this is a bug with Go, we'll need a way to reproduce the problem ourselves. |
@ianlancetaylor MSG is new i don't where invalid pointers?The problem has been hotly discussed. But it seems that the real reason has not been found, and I have this problem again. https://github.com/lxn/walk/pull/493#issue-274104188
|
The code you show isn't valid Go, but, more importantly, the |
@ianlancetaylor I tried to add
|
In order to help you, we'll need a way to reproduce this problem ourselves. |
No reproducer or news for almost a year, I think we can close here. |
golang version 1.15
Windows server 2012
Exception 0xc0000005 0x0 0x1749111c 0x77e47594
PC=0x77e47594
signal arrived during external code execution
syscall.Syscall6(0x7598a5b0, 0x4, 0x27066f8, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...)
C:/Go/src/runtime/syscall_windows.go:201 +0xbb
GoProxy/vendor/github.com/lxn/win.GetMessage(0x27066f8, 0x0, 0x0, 0x0, 0x1)
D:/svn_code/src/GoProxy/vendor/github.com/lxn/win/user32.go:2564 +0x8a
GoProxy/vendor/github.com/lxn/walk.(*FormBase).mainLoop(0x2eb9a000, 0x0)
D:/svn_code/src/GoProxy/vendor/github.com/lxn/walk/mainloop_default.go:20 +0x95
GoProxy/vendor/github.com/lxn/walk.(*FormBase).Run(0x2eb9a000, 0x0)
D:/svn_code/src/GoProxy/vendor/github.com/lxn/walk/form.go:373 +0xa3
main.main()
No problem has been found in win7 environment for the time being. This problem has been found in 2012 server. It's not a startup error, it's other groutines that call programs with a desktop.
The text was updated successfully, but these errors were encountered: