-
Notifications
You must be signed in to change notification settings - Fork 17.5k
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: stack growth after fork #48967
Comments
This fix prevents additional stack checking code from being generated on func efaceOf to avoid unexpected growth of stack in child process. Fixes golang#48967 Signed-off-by: Honsun Zhu <honsun@linux.com>
This fix prevents additional stack checking code from being generated on func efaceOf to avoid unexpected growth of stack in child process. Fixes golang#48967
This fix prevents additional stack checking code from being generated on func efaceOf to avoid unexpected growth of stack in child process. Fixes golang#48967
This fix prevents additional stack checking code from being generated on func efaceOf to avoid unexpected growth of stack in child process. Fixes golang#48967
Change https://golang.org/cl/356109 mentions this issue: |
What version of Go are you using? We should maybe backport this though? A stack growth during a vfork or something sounds pretty bad. |
I'm using go1.17.2 and have also tested it on 1.16.9. Yes we should be backport this, the master branch does not need this patch. |
This fix prevents additional stack checking code from being generated on func efaceOf to avoid unexpected growth of stack in child process. Fixes golang#48967
go/src/runtime/runtime2.go
Lines 211 to 215 in 2feb2cc
Why this func not have
//go:nosplit
?go/src/runtime/proc.go
Lines 446 to 449 in c580180
When setsig call
funcPC
, there will be panic!The text was updated successfully, but these errors were encountered: