Hi. Mine does not get to aforementioned extremes, but it might if my uptimes get longer (which is inhibited by another issue) Well using "ibus-daemon --replace" is nice, although it leaves a zombie behind.
One could actually start or reissue "ibus-daemon --replace" in the limited shell. I use it for similar memory loving apps, like gnome-stardict
Say, start a terminal and execute
$ ulimit -v 307200 -m 20480 #or similar, where -m and -v are the actual memory virtual memories in kb, resp.
and then
$ ibus-daemon --replace
When the greedy python process gets to the maximum limit it exits and the applet is gone, one can then restart ibus-daemon from the same limited shell.
It turns out, that I don't really need that applet, so I am figuring how to dispense with it completely.
Hi. Mine does not get to aforementioned extremes, but it might if my uptimes get longer (which is inhibited by another issue) Well using "ibus-daemon --replace" is nice, although it leaves a zombie behind.
One could actually start or reissue "ibus-daemon --replace" in the limited shell. I use it for similar memory loving apps, like gnome-stardict
Say, start a terminal and execute
$ ulimit -v 307200 -m 20480 #or similar, where -m and -v are the actual memory virtual memories in kb, resp.
and then
$ ibus-daemon --replace
When the greedy python process gets to the maximum limit it exits and the applet is gone, one can then restart ibus-daemon from the same limited shell.
It turns out, that I don't really need that applet, so I am figuring how to dispense with it completely.