Memory leaking problem

[marcinn]

Process called panel-9-wckbutt, which is controlling wck-plugin, is leaking memory. After some time it reaches RES memory usage greater than 3,8G! I'm using notebook and using sleep mode instead of shutting down (uptime is now 9 days). After killing the process wck buttons closes and reappears automatically, and the memory usage is redcued.

Affected version: 0.4.4-1 Xfce: 4.12 Package: https://aur.archlinux.org/packages/xfce4-windowck-plugin/

[timojuez]

affects me too. But it usually takes 200 MB.

[pumpkinlink]

it reached 1.7 gb here today until i noticed my computer was slow because of swapping. i am using version 0.3.1 from a ppa, but i previously tried out the latest release 0.4.4 built myself from this repo and i had the same exact problem. XFCE is version 4.12. I also put my laptop on sleep mode, and currently my uptime is 5 days. The memory map on gnome system monitor shows the leak is happening on the process heap (i dont think that helps very much but anyway)

[timojuez]

If you just kill that big process, the plugin may continue to work. Other alternative to the plugin are xfce starters in the edge with the commands: min: bash -c 'xdotool windowminimize $(xdotool getactivewindow)' max: wmctrl -r :ACTIVE: -b toggle,maximized_vert,maximized_horz close: wmctrl -c :ACTIVE:

unfortunately this always controls the active window and not the maximised one.

2017-02-21 20:53 GMT+02:00 Denis Franco notifications@github.com:

it reached 1.7 gb here today until i noticed my computer was slow because of swapping. i am using version 0.3.1 from a ppa, but i previously tried out the latest release 0.4.4 built myself from this repo and i had the same exact problem. XFCE is version 4.12. I also put my laptop on sleep mode, and currently my uptime is 5 days. The memory map on gnome system monitor shows the leak is happening on the process heap (i dont think that helps very much but anyway)

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/cedl38/xfce4-windowck-plugin/issues/30#issuecomment-281440675, or mute the thread https://github.com/notifications/unsubscribe-auth/AEQRD3eJJT86L9_vJgX5MFf_QuXOuYtuks5rezK3gaJpZM4I_7wN .

[pumpkinlink]

I have temporarily circumvented the problem by installing monit and creating a configuration to monitor both plugin processes and autokill them when they are using too much memory, then adding the monit command to xfce "Session and Startup". My ~/.monitrc file as follows:

# Start monit as a daemon, detach from console. check every 300 seconds.
set daemon 300
check process "panel" matching "libwindowck.so"
    restart program = "/usr/bin/pkill --signal SIGTERM -f -- 'wrapper-1\.0.+libwindowck.so .+windowck-plugin'  "
    if total memory > 300.0 MB for 1 cycle then restart

# I cant use the same name "panel" again as a service name,
# so i used "wrapper-1.0" which works also
check process "wrapper-1.0" matching "libwckbuttons.so"
    restart program = "/usr/bin/pkill --signal SIGTERM -f -- 'wrapper-1\.0.+libwckbuttons.so .+wckbuttons'  "
    if total memory > 300.0 MB for 1 cycle then restart

[baronleonardo]

I have the same problem here, I have no swap active so at some point the system hang completely, and I must force it to poweroff I think the problem is in Window Header - Title

[arseto]

Has this issue addressed yet? I just recently encountered same issue, and yes, it's the Window Header - Title plugin that hogs almost 4GB of RAM. When I wondered why I can't hibernate anymore, my swap partition is full :sweat_smile: .

Sorry for resurrecting old post, I think if the issue is not addressed yet, it should be. Thanks.

[abchk1234]

Its still present in xfce4-windowck-plugin-0.4.6. I use hibernate instead of shutdown. Memory usage of panel-8-wckbutt keeps growing over time.

  1.4 GiB +   1.4 GiB =   2.9 GiB   panel-8-wckbutt

Using with xfce4-panel-4.14.4 and xfwm4-4.14.2 on Slackware Linux.

Tried running it through valgrind using guide, output: 1589200942_valgrind_wckbuttons_8.log

Btw is it necessary to use debug versions of xfce4-panel and xfce4-windowck-plugin to post valgrind output? Thanks.