-
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 close #734
Comments
I don't have any insight into this, I guess it needs some active debugging. If the segfault is happening during kivy's internal stop process then that's probably the first place to look. |
Here's the problem I experienced (with crash in the same place): Nobody destroys the app Window by default. Then long after Python is gone ("Python for android ended."), Java will call back via Workaround: You must call An ideal way to do this is to handle the event in
|
@inclement can you provide details about the basic kivy shutdown design? I guess that the event should be bound to something which cleans up the window without needing user code? |
@cidermole I've also spent a few hours to fixed this issue a couple week ago, this is my patch :- http://pastebin.com/JthasWiG @inclement I will submit PR to Kivy if this is make sense. |
@gooroopy Sorry for the delay replying, and thanks a lot for the patch! I'm not familiar with this part of Kivy's internals, but if you didn't do so already it would be very welcome to open a PR in the kivy repo for it. |
I believe this is no longer happening on p4a master. Recently I was testing this type of thing while getting pause to work with sdl2.0.9 |
When I exit my app (
app.stop()
), a strange segmentation error occurs: http://pastebin.com/F8HEaeipThis is with sdl2 and kivy 1.9.2 dev.
It works fine with pygame, what makes me puzzled.
The requirements list:
requirements = openssl,geopy,plyer,android,tinydb,hostpython2,kivy==master
What could be the reason of this crash?
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: