[Mesa-dev] [Bug 98831] Constantly increasing memory consumption in JavaFX applications

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=98831

--- Comment #6 from Christoph Haag <haagch at frickel.club> ---
This was my test case for the same problem:
https://gist.github.com/ChristophHaag/661be992429b451218e9ee1fb0eacdec

The problematic calls being ImageView.setTranslateX() and
ImageView.setTranslateY() and perhaps ImageView.setRotate(), but I'm not sure
about that anymore.

I first encountered it on Intel Ivy Bridge, but on my RX 480 with current mesa
git I still see the same.

I noticed that the memory leak is basically eliminated when running with dri 2,
i.e. with the environment variable LIBGL_DRI3_DISABLE=1. Other side effects
like slowly raising cpu usage (just let it run 5-10 minutes) and X getting more
laggy (X having 75-80% CPU load) persist though, so it's not a complete
workaround.

With visualvm (the netbeans profiler is basically the same, but has additional
fixes for java 8 lambdas, at least last time I tried it) can be used to show
where the cpu time is spent, like this: https://i.imgur.com/KqZU91l.png
It can also dump the java heap and it turns out that it produces a small file.
So all the memory is not used by the java heap. It's either in mesa or in
JavaFX's native rendering code.


Since this problem is getting so old, someone might be willing to test the
"Mixed Mode CPU Flame Graph" method from
http://www.brendangregg.com/FlameGraphs/cpuflamegraphs.html

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/mesa-dev/attachments/20161123/98ae970d/attachment.html>