! Please note that this is a snapshot of our old Bugzilla server, which is read only since May 29, 2020. Please go to gitlab.xfce.org for our new server !
Significant memory leak, while making input from 2 different keyboards


Description Eugene Voronov 2009-08-25 17:20:38 CEST
To test this bug, we attached 2 keyboards (PS/2 and USB) to one PC with installed XUbuntu 9.04. Each time, when we change the input method (type a symbol from another keyboard) the xfwm4 process eat near 100kb of virtual memory (info from htop). After 1 hour of testing, the xfwm4 process takes near 200Mb of virtual memory and 130Mb resources.
Comment 1 Olivier Fourdan editbugs 2009-08-26 07:10:13 CEST
Can you run xfwm4 in algrind and provide the log? That's very useful to chase memory leaks...
Comment 2 Olivier Fourdan editbugs 2009-08-26 07:10:57 CEST
...and also the version of xfwm4 too as some memleaks have been plugged in 4.6.1.
Comment 3 Eugene Voronov 2009-08-26 10:31:08 CEST
I have tested 4.6.1 too, same result. Do I need to build debug version to run xfwm under valgrind?
Comment 4 Olivier Fourdan editbugs 2009-09-04 08:31:02 CEST
(In reply to comment #3)
> I have tested 4.6.1 too, same result. Do I need to build debug version to run
> xfwm under valgrind?

Yes I guess it helps, along with relevant libraries symbols too.
Comment 5 Steve Dodier-Lazaro editbugs 2014-11-03 16:05:20 CET

I'm looking at old bug reports. If anybody is still experiencing this on 4.12, could they please let the developers know?

Developers: did Xfwm 4.6 use libkeybinder by any chance? I spotted serious memleaks on multiple layout keyboards which occurred at least for Xubuntu users, but libkeybinder is no longer supported. If 4.6 was using it and the codebase has now been switched to something else, it could explain the issue.
Comment 6 tomplatz 2019-07-11 13:44:00 CEST
Created attachment 8760 

Bug #5701

Reported by:
Eugene Voronov
Reported on: 2009-08-25
Last modified on: 2020-05-26


Olivier Fourdan
CC List:
3 users



127 (27.57 KB, application/pdf)
2019-07-11 13:44 CEST , tomplatz
no flags

Additional information