Hi,
ext John Meacham wrote:
> In any case, looking at the memory usage, hildon-input-method takes up
> a whopping 6.3 megs of real ram
That's just RSS. Most of that is Gtk libraries and their dependencies
shared with all the other applications on the device. VmData & VmStk
values from /proc/<IM PID>/status file give a slightly more accurate
value of what RAM is private to input method.
It's still a lot, but not even near 6Mb...
> along with a decent chunk of x resources as reported by xrestop.
Xrestop reports 314KB of Pixmaps for the input method, but once I
close it, only 96KB remains. I think that is the Gtk scratchbuffer
(i.e. reserved by Gtk, not input method) as I can see it also in
/proc/sysvipc/shm file.
> I know I have to create a gtk-immodule, but can't find documentation
> anywhere about how to do that or how to get rid of hildon-input-method
> once I create my gtk-immodule. I am very familier with low level X11
> programming, but not so much with gtk specifics.
I don't think you need to do the Gtk IM-module, I think the IM module
communicates with the keyboard using X messages (i.e. your X11 expertise
will actually help :-)).
The target input method window seems to be told here:
# xprop -root|grep HILDON
_HILDON_IM_WINDOW(WINDOW): window id # 0xc00003
> Also, what keeps respawning the hildon-input-method? I can kill it
> remotely and bask in the extra 6 megs of RAM for a few seconds before
> it restarts without me ever trying to actually use the input method.
See into: /etc/osso-af-init/keyboard.sh
It's started with a watchdog.
- Eero
_______________________________________________
maemo-developers mailing list
[email protected]
https://maemo.org/mailman/listinfo/maemo-developers
