Bug 1276186 may be an acute form of this bug.
I saw both the high CPU usage and extreme RAM usage (about 1 megabyte/second leak).
It happened when I minimized Chrome, but continued long after I killed all the chrome processes.
ibus-ui-gtk3 got up to 2+ gigabytes of ram pretty quickly. I'll attach an apport log.
I guess I could figure out how to valgrind the app by disabling ibus in System Settings / Language Support,
then following https://code.google.com/p/ibus/wiki/IBusStartUpTroubleShooting,
or maybe by looking at the startup hook installed by im-config and modifying it.
But since I don't need an input method, I may just live with ibus disabled.
Bug 1276186 may be an acute form of this bug.
I saw both the high CPU usage and extreme RAM usage (about 1 megabyte/second leak).
It happened when I minimized Chrome, but continued long after I killed all the chrome processes.
ibus-ui-gtk3 got up to 2+ gigabytes of ram pretty quickly. I'll attach an apport log.
I guess I could figure out how to valgrind the app by disabling ibus in System Settings / Language Support, /code.google. com/p/ibus/ wiki/IBusStartU pTroubleShootin g,
then following https:/
or maybe by looking at the startup hook installed by im-config and modifying it.
But since I don't need an input method, I may just live with ibus disabled.