One could say that basing anything critical on something that is very openly described as experimental is a touch foolhardy.Neex wrote: ↑Wed Sep 26, 2018 9:58 amJust putting my hand up saying that we've invested heavily in RasPi for our product, and Kivy as the provider for our UI. As we near product launch, and discover that our UI is failing because of a memory leak, we are extremely concerned. Can anyone provide a status, schedule and workaround? Many thanks.
Workaround - build mesa and libdrm for yourselves. https://github.com/anholt/mesa/wiki/Bui ... sa-for-VC4
Schedule - there is a backport of mesa 18.1.6 for Raspbian Stretch (https://packages.debian.org/stretch-bac ... begl-mesa0).
If someone fancied either
a) testing 18.1.6
b) providing a SIMPLE test case that can be tested by others
then it may be possible to update Raspbian to that (it all depends on the number of dependencies that also need updating).
Stability is the name of the game. It's nigh on impossible to test everything that relies on Mesa, hence the hand-off approach to updating it randomly.