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.

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

crypto/internal/boring: found pointer to free object/found bad pointer in Go heap #54604

Closed
rolandshoemaker opened this issue Aug 22, 2022 · 3 comments
Closed

crypto/internal/boring: found pointer to free object/found bad pointer in Go heap #54604

rolandshoemaker opened this issue Aug 22, 2022 · 3 comments
Assignees
@mknyszek
Labels
compiler/runtime Issues related to the Go compiler and/or runtime. FrozenDueToAge NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided.
Milestone
Go1.20

Comments

@rolandshoemaker
Copy link
Member

While running the Wycheproof test suite to debug #54558, I managed to trigger a fatal error: found pointer to free object and a fatal error: found bad pointer in Go heap panic. In particular this seemed to occur frequently when using rsa.DecryptOAEP (and the internal boring.DecryptOAEP), but I was able to trigger it elsewhere as well (i.e. rsa.SignPKCS1v15 etc). Unfortunately after debugging this for a while the issue managed to magically disappear, and I have been unable to trigger it again.

Opening this issue in case a cause is obvious to anyone. I'll post traces if I'm able to trigger it again.

cc @rsc
@rolandshoemaker rolandshoemaker added the compiler/runtime Issues related to the Go compiler and/or runtime. label Aug 22, 2022
@dr2chase dr2chase added the NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. label Aug 24, 2022
@dr2chase
Copy link
Contributor

@mknyszek

@mknyszek
Copy link
Contributor

@randall77 and I believe that this is probably fixed by https://go.dev/425194, so I'm just going to leave this in WaitingForInfo to see if it shows up again.

@mknyszek mknyszek added the WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided. label Aug 24, 2022
@mknyszek mknyszek self-assigned this Aug 24, 2022
@mknyszek mknyszek added this to the Go1.20 milestone Aug 24, 2022
@mknyszek
Copy link
Contributor

Since it's been a week and we're pretty sure this is fixed, I'm going to close it optimistically.

@golang golang locked and limited conversation to collaborators Aug 31, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@mknyszek mknyszek

Labels
compiler/runtime Issues related to the Go compiler and/or runtime. FrozenDueToAge NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided.
Projects
None yet
Milestone
Go1.20
Development

No branches or pull requests
4 participants
@mknyszek @dr2chase @rolandshoemaker @gopherbot