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
Segfault when running touch tracer app #201
Comments
Seems to happen when you put a lot of fingers on the touchpad here are the error messages from the terminal: [ERROR ] [OSC ] Address 0.0.0.0:3333 already in use, retry in 2 second examples > [ERROR ] [OSC ] Address 0.0.0.0:3333 already in use, retry in 2 second examples > [ERROR ] [OSC ] Address 0.0.0.0:3333 already in use, retry in 2 second |
Thanks ! |
Well I just downloaded the (binary?) osx Version from the kivy website. Maybe I'll check it out from github later. Do you not have access to a Mac yourself? |
We do. Your log is not complete, however. Please paste everything from start to finish. |
Here it is: Kivy > kivy examples/demo/touchtracer/main.py |
I would like to add that a crash also is reproducible in touchtracer on my OSX 10.6.8. I downloaded the 1.0.7 dmg image Complete stacktrace: http://paste.pocoo.org/show/444275/ It seems to happen in the vbo.so module. Edit: In addition, the error is triggered by the drawing routines since, when I take out code from from all 4 on_* handlers in Touchtracer class , it doesn't happen: http://paste.pocoo.org/show/444278/ 2nd edit: If I only take out the code that draws the label, it does not crash anymore. So that's good news that narrows it down a bit: http://paste.pocoo.org/show/444282/ 3rd edit: The crash seems to be caused by the three lines of code inside on_touch_up handler. If that code is executed, the app doesn't crash. http://paste.pocoo.org/show/444431/ That code only removes the group and the widget so that the drawn lines and labels disappear when a user raises their finger. 4th edit: this line causes the crash |
Thanks a lot for the analysis. I still doesn't understand how to trigger it :/ Can you tell me if it's as soon as your using it ? One test i would like you to do too, is to check how many times the on_touch_up is called ? |
Ow ow ow ow ow ! I see why it's crashing. I don't think it's an issue about remove_widget (is it random or not ?) The 6 libGL.dylib 0x00007fff8769b022 glDeleteBuffers + 18 Never do gl command in another thread than main thread... Now why it's happening, i've absolutly no fucking idea >_< |
That's very weird. I'll do the same approach than texture: put the vbo deletion in a list, and trigger the list in a Clock, from the main thread. Thanks a lot for reporting ! |
Happens randomly - yes, but always on touch_up . If the remove_widget is commented out, it works forever - it does not crash. Also, if I keep my finger on the touchpad the whole time and don't lift it up, it runs forever as well. ... |
areksb, can you pull the master version, recompile, and test if it's works better for your case ? Since i didn't be able to trigger it, i want to ensure that this fix will do the job. Thanks ! |
Kivy segfaults when running the touchtracer app. This happens in Mac OS X Snow Leopard with the Kivy development stream from github as well as the stable versions. Looks like a memory leak.
http://paste.pocoo.org/show/441545/
The text was updated successfully, but these errors were encountered: