Matt MassicotteMay 11, 2024
@libei Can you see the actual crash type?
Show threadBei LiMay 12, 2024
@mattiem Yes, but I can't get more information either.
Show threadMatt MassicotteMay 12, 2024
@libei Ok so bad access. And that memory address is quite something. Maybe try running with the memory debugging tools on, like guard malloc and zombies?
Show threadBei Li
@mattiem I can't reproduce it in local, so help from debugging tools are unavailable. 🤷‍♂️
May 12, 2024 at 10:00amWeb
Show threadMatt MassicotteMay 12, 2024
@libei I’m not so sure. This looks like it could be heap corruption, which is quite common. When that happens, usually the crash is a victim of a long-gone root problem not captured by the stack trace. I’d definitely still try.
Show threadBei LiMay 12, 2024
@mattiem OK I could have a try. But this code path is super early, there's no much code run before it.
Show threadMatt MassicotteMay 12, 2024
@libei Yeah I’m not sure! I wish I had a better suggestion…