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
runtime: fatal error: stoplockedm: inconsistent locking #18178
Comments
This is the only instance of "stoplockedm: inconsistent locking" ever. I wonder if this is related to #15658 and is just random memory corruption. There's a lot of forking/execing going on around this test, though the crashing binary itself didn't fork/exec. Obviously it's too late for this instance, but I wonder if it would be possible to get core dumps or something out of the builders for runtime crashes. Something to make post-mortem debugging easier than feeling around in the dark. |
Closing since this has only happened once. Reopen if we ever see this again. |
I have get the same issue, but it is random error, I made some changes inside the runtime but nothing that affect this part directly (I mean the stoplockedm), but as I'm compiling the whole language many times per day, so I'm getting this error each 5 of 10 times when I run ./all.bash. |
This issue was closed a long time ago. Whatever you are encountering, it is a different problem. Please open a new issue. But please only open the issue if you are encountering a problem with unmodified sources. If you only encounter the problem with your runtime modifications, then the problem is almost certainly due to your modifications. |
I do not believe that any change that I made has cause this error, as you see @bradfitz got the same, with the same version go1.8, I'll not open a new issue cause I made some modifications at runtime, but I'm still comparing with a stable release of 1.8, if I catch this error again with the stable version I will report. |
freebsd-386-gce101 at 6270c5a
https://build.golang.org/log/ce4de82bc9e073e9f2f95b49b2f20ce6954d1876
Austin, is this new?
The text was updated successfully, but these errors were encountered: