destroyScene causes Fatal signal 11 (SIGSEGV) - Android

Solar2D Daily Builds and Public Releases
#1

Sometimes right after destroyScene is called, the application quits and prints this error in logcat.

05-14 13:43:43.162: I/Corona(9486): destroyScene postLobbySingle  
05-14 13:43:43.166: A/libc(9486): @@@ ABORTING: INVALID HEAP ADDRESS IN dlfree  
05-14 13:43:43.169: A/libc(9486): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1)  
05-14 13:43:43.169: D/dalvikvm(9486): GC\_CONCURRENT freed 6984K, 43% free 9706K/16839K, paused 1ms+3ms  
05-14 13:43:43.595: I/DEBUG(78): \*\*\* \*\*\* \*\*\* \*\*\* \*\*\* \*\*\* \*\*\* \*\*\* \*\*\* \*\*\* \*\*\* \*\*\* \*\*\* \*\*\* \*\*\* \*\*\*  
05-14 13:43:43.595: I/DEBUG(78): Build fingerprint: 'google/soju/crespo:4.0.4/IMM76D/299849:user/release-keys'  
05-14 13:43:43.599: I/DEBUG(78): pid: 9486, tid: 9502 \>\>\> test.test \<\<\<  
05-14 13:43:43.603: I/DEBUG(78): signal 11 (SIGSEGV), code 1 (SEGV\_MAPERR), fault addr deadbaad

This never occurred when we didn’t use storyboard.removeScene and allowed all the images to remain in memory. All of the timers and listeners are stopped and removed in exitScene. There is also no code in destroyScene. We are using daily build 813 and have no problems when using the simulator.

Any thoughts? [import]uid: 88922 topic_id: 26293 reply_id: 326293[/import]

#2

Would you be able to file a bug report with a zipped project file we can run that demonstrates this issue, please?

The other thing I’d be interested in is whether or not you are having any issues on iOS with the same project? [import]uid: 52491 topic_id: 26293 reply_id: 106879[/import]

#3

We have no problem with the iOS version. I will try to make a sample project. [import]uid: 88922 topic_id: 26293 reply_id: 108026[/import]