Jump to content

[TOPIC: topicViewTemplate]
[GLOBAL: userSmallPhoto]

Need help with native crash.
Started by dodi_games Oct 02 2019 04:49 PM

1 reply to this topic
[TOPIC: post.html]


[GLOBAL: userInfoPane.html]
  • Contributor

  • 408 posts
  • Corona SDK

Today Google Play Console data of my game was updated and I could see that I have several crash reports with the following information:

Native crash at signal 11 (SIGSEGV), code 1 (SEGV_MAPPER)

Attached File  crash_1.jpg   21.23KB   0 downloads


I'm using Corona Simulator 2019.3523 (2019.9.7)


Android 6.0

Android 7.0

Android 8.1


This is new for me and I don't know how to start debugging. In addition I have never experienced a crash testing the game myself.


Any help is welcome

Thanks in advance


[TOPIC: post.html]

Rob Miracle

[GLOBAL: userInfoPane.html]
Rob Miracle
  • Moderator

  • 26,625 posts
  • Enterprise

You will need to get the whole stack trace and post it here using a service like pastebin.com.


In general a Signal 11, SIGSEGV is knows as a "Segment violation".  This is where you try to access memory you don't have access too. Generally Corona is pretty free from these, but we can't be responsible for problems in upstream libraries, other than trying to harden the values we pass to them.  


One way you used to be able to get Corona to crash was to have a function in Scene A that was attached to a timer, or an onComplete listener, then go to a new scene and delete the old scene. But the timer/onComplete function is still going (it wasn't stopped when leaving the scene), so the function code gets blown away but the onComplete/timer still tries to call that function. BOOM Segment Violation. They are really hard to track down. 


Anyway, we can't do much without seeing the entire error dump.