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.

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: occasional "exit status 0xc0000005" on windows-386-2012 builder #54187

dmitshur opened this issue Aug 1, 2022 · 4 comments
compiler/runtime NeedsInvestigation


Copy link

dmitshur commented Aug 1, 2022

Observed once in a TryBot run on CL 420675:

exit status 0xc0000005
FAIL	runtime	18.548s


Searching around doesn't find this particular exit code, though there are similar ones like in issue #41450. That exit code seems to be a pretty generic "Application Error" failure, so given the rare occurrence maybe there's not much that can be done.

CC @golang/runtime.

@dmitshur dmitshur added the NeedsInvestigation label Aug 1, 2022
@dmitshur dmitshur added this to the Backlog milestone Aug 1, 2022
@gopherbot gopherbot added the compiler/runtime label Aug 1, 2022
Copy link

mknyszek commented Aug 3, 2022

I think that error code is specifically a segfault, likely an unrecoverable one (maybe in the win32 libraries or something). We should look into this. How rare is the failure? Is this the only one?

Copy link
Contributor Author

dmitshur commented Aug 3, 2022

It's the only one I've seen so far; we can try greplogs or similar tools to look if there've been more.

Copy link

prattmic commented Aug 3, 2022


This is a failure similar to #52647. I'm not sure if it is related to this.

Copy link

mvdan commented Aug 11, 2022

Also on for, a small change in go/printer:

            > go list -deps -f '{{.Module}}' ./subpkg
            [exit status 0xc0000005]
            FAIL: testdata\script\mod_symlink.txt:10: unexpected command failure

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
compiler/runtime NeedsInvestigation
Status: Todo

No branches or pull requests

6 participants