-
Notifications
You must be signed in to change notification settings - Fork 40
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
Kivy apps crash - need mesa version to fix #106
Comments
From your linked bug reports, it sounds like you're not using the Mesa driver at all ("Found brcmEGL and brcmGLES library filesfor rpi platform at /opt/vc/lib/" and your discussion of config.txt gpu_mem settings). |
Can you open your own bug report with your specific issue with the app using full KMS mode, and how to reproduce it? |
Actually kivy is always compiling against broadcom drivers. I opened a PR adding an option to build against mesa vc4 here kivy/kivy#6026. We should continue at #116 for discussing rpi/kivy issues |
For about a month now, we have been trying to fix a Kivy memory leak by compiling older known-to-work mesa drivers and have come to the conclusion that running Kivy fails with a majority of the drivers provided from the repository. We also understand why the drivers haven't been upgraded recently. If you could be so kind to help us compile the drivers so they will work, we would be truly appreciative.
Compiling from "git freedesktop" makes sure all errors go away but the drivers are still very faulty. For example, if you run glxgears to test you will see that the bigger the window is the more erratic it gets. To recreate our environment, we have provided build scripts we have been using, in the link below.
https://pastebin.com/wujcsvLS
The test app we're using that eventually fails, is at the link below. It uses JPG and PNG images contained in the /home/pi/pictures folder.
https://gist.github.com/frankgould/4e217f77b4b16d147e1297e478d652f2
This issue has been documented in some of the following github forums:
kivy/kivy#4542
kivy/kivy#4662
kivy/kivy#5664
The text was updated successfully, but these errors were encountered: