Can you see the actual crash type?

Yes, but I can't get more information either.

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?

I can't reproduce it in local, so help from debugging tools are unavailable.

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.

OK I could have a try. But this code path is super early, there's no much code run before it.