Skip to content

runtime: SIGSEGV in (*fixalloc).alloc on freebsd-amd64-12_2 builder #46103

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.

Sign up for GitHub

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

Jump to bottom
Closed
bcmills opened this issue May 11, 2021 · 4 comments
Closed

runtime: SIGSEGV in (*fixalloc).alloc on freebsd-amd64-12_2 builder #46103

bcmills opened this issue May 11, 2021 · 4 comments
Labels
FrozenDueToAge NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Milestone
Backlog

Comments

@bcmills
Copy link
Contributor

bcmills commented May 11, 2021 

##### GOMAXPROCS=2 runtime -cpu=1,2,4 -quick
fatal error: unexpected signal during runtime execution
[signal SIGSEGV: segmentation violation code=0x1 addr=0x84d3bbb40 pc=0x41f5fb]

runtime stack:
runtime.throw({0x67f3aa, 0x2a})
	/tmp/workdir/go/src/runtime/panic.go:1198 +0x74 fp=0x7fffdebf3cf8 sp=0x7fffdebf3cc8 pc=0x43ef14
runtime.sigpanic()
	/tmp/workdir/go/src/runtime/signal_unix.go:719 +0x4a5 fp=0x7fffdebf3d58 sp=0x7fffdebf3cf8 pc=0x457645
runtime.(*fixalloc).alloc(0x845510)
	/tmp/workdir/go/src/runtime/mfixalloc.go:72 +0x3b fp=0x7fffdebf3d98 sp=0x7fffdebf3d58 pc=0x41f5fb
runtime.allocmcache.func1()
	/tmp/workdir/go/src/runtime/mcache.go:88 +0x48 fp=0x7fffdebf3dc0 sp=0x7fffdebf3d98 pc=0x41b0c8
runtime.allocmcache()
	/tmp/workdir/go/src/runtime/mcache.go:86 +0x58 fp=0x7fffdebf3df8 sp=0x7fffdebf3dc0 pc=0x41b018
runtime.(*p).init(0xc00016e800, 0x10)
	/tmp/workdir/go/src/runtime/proc.go:4835 +0x114 fp=0x7fffdebf3e18 sp=0x7fffdebf3df8 pc=0x44c9b4
runtime.procresize(0x64)
	/tmp/workdir/go/src/runtime/proc.go:5011 +0x3a9 fp=0x7fffdebf3ec8 sp=0x7fffdebf3e18 pc=0x44d2a9
runtime.startTheWorldWithSema(0x0)
	/tmp/workdir/go/src/runtime/proc.go:1256 +0xa5 fp=0x7fffdebf3f28 sp=0x7fffdebf3ec8 pc=0x4447e5
runtime.startTheWorld.func1()
	/tmp/workdir/go/src/runtime/proc.go:1093 +0x26 fp=0x7fffdebf3f48 sp=0x7fffdebf3f28 pc=0x4751a6
runtime.systemstack()
	/tmp/workdir/go/src/runtime/asm_amd64.s:383 +0x49 fp=0x7fffdebf3f50 sp=0x7fffdebf3f48 pc=0x479d69

2021-05-10T23:42:56-5c48951/freebsd-amd64-12_2

CC @mknyszek @prattmic
@bcmills bcmills added the NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. label May 11, 2021
@bcmills bcmills added this to the Backlog milestone May 11, 2021
@bcmills
Copy link
Contributor Author

bcmills commented May 11, 2021

I could only find one occurrence of this in the logs — it could be either a recent regression or a rare failure mode.

@prattmic
Copy link
Member

Based on the line number, it looks like this is a bad value of f.list. This should be the address of something that originally came from fixalloc.alloc's persistentalloc, which should never be freed. So I don't see an obvious cause here, though I'm curious if 0x84d3bbb40 is in the typical range of persistentalloc on freebsd-amd64.

@prattmic
Copy link
Member

FWIW, on a freebsd-amd64-12_2 gomote, I'm seeing all fixallocs between approximately 0x800000000 and 0x830000000, which is fairly close to the crash address, though I didn't see any as high as 0x840000000

This was referenced May 18, 2021
Closed
Closed
@mknyszek
Copy link
Contributor

Closing as a duplicate of #46272.

@prattmic prattmic mentioned this issue Jul 20, 2021
Closed
@golang golang locked and limited conversation to collaborators May 19, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
FrozenDueToAge NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Projects
None yet
Milestone
Backlog
Development

No branches or pull requests
4 participants
@mknyszek @prattmic @bcmills @gopherbot