You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Looks like this was caused by @rsc's change to NumGoroutine in fac8202. GoroutineProfile checks that the caller passed in enough room for NumGoroutine() stacks and then iterates over allgs to collect stacks, but since NumGoroutine() now omits system goroutines, it will return less than the number of Gs in allgs. If the slice passed in by the caller is big enough for non-system goroutines, but too small for all goroutines, GoroutineProfile will panic.
The previous CL is the real fix. This one is just insurance.
Fixes#14046 again.
Change-Id: I553349504bb1789e4b66c888dbe4034568918ad6
Reviewed-on: https://go-review.googlesource.com/18977
Reviewed-by: Austin Clements <austin@google.com>
Steps to reproduce:
(port and hostname is obviously unimportant, but TLS is required)
Environment:
Server that reproduces the issue (requires a cert.pem and key.pem file):
Trace:
The text was updated successfully, but these errors were encountered: