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.