runtime: unexpected return pc for runtime.(*mheap).alloc #35328
Comments
@randall77 what do you think? Should this block the beta coming up in December? |
This definitely blocks the release, a compiler crash in the runtime alloc path is bad. |
I only encountered this crash once, and haven't seen it again. I should also mention I haven't actively tried to reproduce it; I was in the middle of some work, and only filed the issue so that it wasn't forgotten. Yes, you should be able to If you don't succeed in reproducing the crash, I can try to hammer it later and see if I manage to hit it again. |
Thanks. I'll fold this into the memory corruption super-bug. I'm going to close this issue since nobody has been able to reproduce it. |
Apologies if this is a duplicate of an existing issue. I saw some similar open and closed issues, but none referenced the same function, so I'm opening a new issue to be safe.
Full panic output:
The text was updated successfully, but these errors were encountered: