https://bugs.kde.org/show_bug.cgi?id=440312
Bug ID: 440312
Summary: Severe memory leak with kwin wayland and javafx app
with es2 ( not on kwin x11 )
Product: kwin
Version: git master
Platform: Other
OS: Linux
Status: REPORTED
Severity: major
Priority: NOR
Component: wayland-generic
Assignee: kwin-bugs-n...@kde.org
Reporter: pereira.a...@gmail.com
Target Milestone: ---
SUMMARY
Hi,
This is a weird bug, but from all my testing ( more than a week trying to find
out what was happening ), its a bug that only happens on kwin wayland ( not on
x11 ).
So, I have to use an javafx proprietary app, that when using with kwin wayland,
works completly fine, until .... screensaver activates and turns off the
monitors. By screensaver, I mean just the power idle setting to turn the
monitors off, not any fancy screensaver effect.
What happens is that the app is running fine, usually using about 1GB/2GB of
ram ( I have 16GB, so lots of free ram ). As soon as the screensaver activates
( this can be a 1 minute idle timeout or 1 hour, doesn't matter ), in seconds,
all ram is filled and oom daemon either starts killing or ( if oom daemon
disabled ) the computer gets unresponsive. It fills around 13/14 GB of ram and
4 GB of swap space in seconds.
I am writting this bug report on kwin wayland, because this doesn't happen on
kwin X11. It also doesn't happen on gnome wayland. It also doesn't happen on
sway.
Also this only happens when javafx is using es2 gpu acceleration ( doesn't
happen on software mode, but software mode is almost unusable, the app is very
graphic intensive ).
I have tested also with kde stable releases on gentoo and arch, and kde master
git on opensuse.
I also tried the latest jdk different GC's and with different heap memory
settings.
I understand that this is not much info or that its hard to say that is not a
bug elsewhere. But the bug is reproducible. Unfortunatly, its a proprietary
app. I will try to find an open source javafx app to make it easier to be
reproducible by others.
Please let me know what further steps I can take to track this issue and
provide better info.
STEPS TO REPRODUCE
1. start app
2. dont touch computer to let screensaver kick in
3. watch in another computer through ssh memory get completly filled seconds
after monitors turn off
OBSERVED RESULT
Memory starts getting completly filled and all swap is used. OOM either kicks
in and kills apps or computer gets unresponsive.
EXPECTED RESULT
Like what happens on kwin x11, gnome wayland or sway... memory keeps about the
same after screensaver as before.
SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma:
(available in About System)
KDE Plasma Version:
KDE Frameworks Version:
Qt Version:
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
