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.
Can you run xfwm4 in algrind and provide the log? That's very useful to chase memory leaks...
...and also the version of xfwm4 too as some memleaks have been plugged in 4.6.1.
I have tested 4.6.1 too, same result. Do I need to build debug version to run xfwm under valgrind?
(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.
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.
Created attachment 8760