Weird crash, I have no clue what I did wrong. 🫠

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.

Bei Li

@libei@mastodon.social

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

May 12, 2024 at 10:19:42 AM
(Edited)
Web

Yeah I’m not sure! I wish I had a better suggestion…

Elk Logo

Welcome to Elk!

Elk is a nimble Mastodon web client. You can login to your Mastodon account and use it to interact with the fediverse.

Expect some bugs and missing features here and there. Elk is Open Source and we're actively improving it as a community project. Join us and let's build it together!

If you'd like to report a bug, help us testing, give feedback, or contribute, reach out to us on GitHub and get involved.

To boost development, you can sponsor the Team through GitHub Sponsors. We hope you enjoy Elk!

Anthony FuDaniel RoeTAKAHASHI Shuuji三咲智子 Kevin DengPatakJoaquín Sánchez

The Elk Team