EXC_BAD_ACCESS ios crash app error with Protobuf oneOf
See original GitHub issueIt’s hard to understand but iOS app crash error immediately after launch app with EXC_BAD_ACCESS
at kotlinx.cinterop#<get-cstr>__at__kotlin.String(){}kotlinx.cinterop.CValues<kotlinx.cinterop.ByteVarOf<kotlin.Byte>>
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
EXC_BAD_ACCESS in decodeMessage(decoder:) due to ...
Our crash happens in the decodeMessage(decoder:) method of a message containing a oneof with lots of cases. From what I can tell the...
Read more >Crash : Outlined Destroy Of Object | Apple Developer Forums
I am getting a weird crash that I have not been able to figure out. ... To get one you'll need to run...
Read more >(iOS) Crash in GPBDescriptor on initing a message
to Protocol Buffers. Hello,. We're unable to instantiate a Message in our iOS app using GPB. Error. Thread 1: EXC_BAD_ACCESS (code=2, address=0x21dba056d0).
Read more >Google Protobufs in iOS app crashing at GPBDescriptor
Running our Prod target crashes in the constructor of any GPBMessage object. It crashes within the + (GPBDescriptor *)descriptor function of the ...
Read more >Blog - Plausible Labs
As developers, when one of our applications crashes, we would like ... We are going to be talking mainly about crashes of iOS...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thank you for the small test case @pddkhoa-fossil! I’ll try to reproduce the error and see if I can figure out why it’s happening.
@pddkhoa-fossil That’s great! In my experience the Kotlin/Native runtime is still undergoing pretty big changes and improvements with every release. My guess is that the code generated by pbandk was triggering some kind of bug in the Kotlin/Native 1.4 runtime that has since been fixed in 1.6.0. We’ve seen a fair number of Kotlin/Native compiler bugs triggered by pbandk-generated code in the past and have had to implement some workarounds in the pbandk code generator. Every Kotlin release gets a little bit better 😄
Let us know if you run into any other issues/crashes. Otherwise I’ll go ahead and close this issue.