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: failures with "cannot map pages in arena address space" on freebsd-amd64-race since 2021-11-09 #49687

bcmills opened this issue Nov 19, 2021 · 1 comment


Copy link

@bcmills bcmills commented Nov 19, 2021

fatal error: runtime: cannot map pages in arena address space

runtime stack:
runtime.throw({0x9f747c?, 0x0?})
	/tmp/workdir/go/src/runtime/panic.go:992 +0x71
runtime.sysMap(0x0, 0x40ccc9?, 0xc000611358?)
	/tmp/workdir/go/src/runtime/mem_bsd.go:76 +0xa5
runtime.(*mheap).grow(0xdd4320, 0xc000611200?)
	/tmp/workdir/go/src/runtime/mheap.go:1404 +0x225
runtime.(*mheap).allocSpan(0xdd4320, 0x0, 0x0, 0x0)
	/tmp/workdir/go/src/runtime/mheap.go:1170 +0x171
	/tmp/workdir/go/src/runtime/mheap.go:912 +0x65
	/tmp/workdir/go/src/runtime/asm_amd64.s:469 +0x49

greplogs --dashboard -md -l -e '^fatal error: runtime: cannot map pages in arena address space' --since=2021-01-01


Copy link
Member Author

@bcmills bcmills commented Nov 19, 2021

I suspect that this may be due to memory exhaustion; as noted in #49347 (comment), the freebsd-amd64-race builder has a higher CPU-to-RAM ratio than most of the other -race builders, which may cause its GOMAXPROCS to be fairly aggressive for the amount of available memory.


Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant