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,cmd/compile: exit status 0xc0000374 (STATUS_HEAP_CORRUPTION) on windows-amd64-longtest #52647

Open
bcmills opened this issue May 2, 2022 · 3 comments
Assignees
Labels
NeedsInvestigation OS-Windows release-blocker
Milestone

Comments

@bcmills
Copy link
Member

@bcmills bcmills commented May 2, 2022

XXXBANNERXXX:Test execution environment.
# GOARCH: amd64
# CPU: Intel(R) Xeon(R) CPU @ 2.20GHz
# GOOS: windows
# OS Version: 10.0.14393
go tool compile: exit status 0xc0000374

go tool dist: FAILED: go list -f={{if .Stale}}	STALE {{.ImportPath}}: {{.StaleReason}}{{end}} std: exit status 1

According to https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-erref/596a1078-e883-4972-9bbc-49e60bebca55, this exit code means:

0xC0000374
STATUS_HEAP_CORRUPTION
A heap has been corrupted.


greplogs --dashboard -md -l -e \(\?ms\)\\Awindows-.\*0xc0000374

2022-04-27T14:23:28-f0c0e0f/windows-amd64-longtest

Since this has only been seen once, leaving on the backlog to see whether this is a recurring pattern or a one-off fluke.
(CC @golang/runtime)

@bcmills bcmills added OS-Windows NeedsInvestigation labels May 2, 2022
@bcmills bcmills added this to the Backlog milestone May 2, 2022
@bcmills
Copy link
Member Author

@bcmills bcmills commented May 9, 2022

Re-running the scan due to the possibility of failures masked by #52591:

greplogs --dashboard -md -l -e \(\?ms\)\\Awindows-.\*0xc0000374
2022-05-06T14:33:48-119da63/windows-amd64-longtest
2022-04-27T14:23:28-f0c0e0f/windows-amd64-longtest

@bcmills
Copy link
Member Author

@bcmills bcmills commented May 9, 2022

That's two matching failures within the Go 1.19 cycle (and even within the past couple weeks!) on windows/amd64, which is a first-class port, and none before that. Looks like a release-blocking regression to me.

(CC @golang/windows)

@bcmills bcmills removed this from the Backlog milestone May 9, 2022
@bcmills bcmills added this to the Go1.19 milestone May 9, 2022
@bcmills
Copy link
Member Author

@bcmills bcmills commented May 11, 2022

One more:
greplogs --dashboard -md -l -e \(\?ms\)\\Awindows-.\*0xc0000374 --since=2022-05-07
2022-05-10T15:43:40-8fdd277/windows-amd64-longtest

@prattmic prattmic self-assigned this May 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
NeedsInvestigation OS-Windows release-blocker
Projects
Status: Todo
Development

No branches or pull requests

2 participants