Problem with terminating apps on Android

Okay, I got this weird problem I just cant figure out.

I am developing a game for iOS and Android, and it works perfectly on iOS. It also works perfectly on my HTC and my Sony Xperia, however on my Galaxy S3 it does not.

Or well it does. It works fine UNTIL you force quit the game. After you force quit and start the app again, it loads the first scene (my menu) like it should, but when I hit “new game”, which loads the first scene in the actual game. It crashes.

The crash log gives me this me this: (and a lot more, but this seems to be the key message?)

I/DEBUG   ( 1910): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 00000000

I dont know what it means, but general googling seems to say it’s something about memory, but I am pretty clueless as the what the actual problem can be, since it ONLY happens after you force quit the game, and only on one of three devices I have tested it on. It doesnt always happen either, but at least 50% of the time after a force quit, it crashes when restarting, somewhere while loading the main game scene. It’s really strange…

I am thinking something weird is happening when the App is force quit? But what? And is there a way to control it?

Will running something in: OnApplicationQuit() help? Or is that not called when you force quit something?

I mean force quitting is the way to quit applications on Android devices isnt it? Thats what most people do? So it’s probably bad if it means a crash the next time you run the game.

Have anyone experienced something similar, or a similar crash log message? And have an idea what to do about it?

Thanks in advance

Please submit a bug report with a minimal sample project (if possible, will be very helpful) that reproduces this problem, following these guidelines and additional information:

http://unity3d.com/BugReportingFAQ

http://issuetracker-staging.unity3d.com/

The bug reporting tool is next to the Unity executable if you can’t run it from the editor. Our QA team will review the issue as soon as possible, and then assign it to our developers. Having the bug report is the only way this problem can be fixed.