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
goroutine 1299607 [runnable]:
context.(*valueCtx).Err(0xc00a52c3c0?)
<autogenerated>:1 +0x3e
context.(*valueCtx).Err(0x48860a?)
<autogenerated>:1 +0x2a
context.(*valueCtx).Err(0x48860a?)
<autogenerated>:1 +0x2a
context.(*valueCtx).Err(0x48860a?)
<autogenerated>:1 +0x2a
... repeats many many many times ...
...additional frames elided...
created by
....one_of_my_functions()
somefile.go:2092 +0x4a5
What did you expect to see?
Not something that appears to be infinite recursion.
What did you see instead?
A very deep callstack that I cannot explain, particularly since the standard Err() function doesn't take a parameter. I haven't yet found the code for valueCtx but it didn't come up via definition link in vscode.
The app in question degrades in performance the longer it runs, and it appears this may be due to increasing load from some kind of processor heavy tight loop somewhere. So I went looking at stack traces and found the above oddity.
The text was updated successfully, but these errors were encountered:
There is no infinite recursion. Sounds more like you've created a very long chain of contexts in your app.
Unlike many projects, the Go project does not use GitHub Issues for general discussion or asking questions. GitHub Issues are used for tracking bugs and proposals only.
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Cannot test this easily.
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
I called runtime.Stack() and saw:
What did you expect to see?
Not something that appears to be infinite recursion.
What did you see instead?
A very deep callstack that I cannot explain, particularly since the standard Err() function doesn't take a parameter. I haven't yet found the code for valueCtx but it didn't come up via definition link in vscode.
The app in question degrades in performance the longer it runs, and it appears this may be due to increasing load from some kind of processor heavy tight loop somewhere. So I went looking at stack traces and found the above oddity.
The text was updated successfully, but these errors were encountered: