-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
App crash on resume with new tool chain #646
Comments
I was asking about it on #kivy-dev last night. On Tue, Feb 16, 2016 at 3:44 AM, Alexander Taylor [email protected]
|
No, that crashing issue was due to bad locking (one thread held the GIL while waiting on another lock, and that code which released that lock needed the GIL to do so). |
Could that be the case if the image can't be found for loading screen? |
That would be weird. It starts cold just fine. On Tue, Feb 16, 2016 at 1:10 PM, Mathieu Virbel [email protected]
|
@inclement It doesn't look like anything pushed since then has anything to do with this problem, but I'll try pulling all changes and building from clean environment when I get home just to be sure. |
I did a pull and ran it from clean environment. Got this error: [INFO]: The selected bootstrap is sdl2 |
Ok, the error in my previous comment was fixed in 7881a0b. |
I rebuilt this and now it seems to work just fine. Thanks for your patience. |
After I switched to the new toolchain my app now crashes when resuming with the error:
"java.lang.RuntimeException: Unable to start activity ComponentInfo{edword.test.edword/org.kivy.android.PythonActivity}: java.lang.IllegalStateException: The specified child already has a parent. You must call removeView() on the child's parent first."
I get a popup that says the application has stopped. I hit OK and the application restarts.
logcat: http://pastebin.com/tXEkfPy6 (had to trim for size, everything important should be there)
buildozer spec: http://pastebin.com/WCbU96TM
buidozer log: http://pastebin.com/negsytP7
Tested on an LG Volt (Android 4.4)
The text was updated successfully, but these errors were encountered: