Hi,
I just took a look at focuswriter (a nice Qt texteditor) and found that it brought the system to its knees as soon as I start typing, with plasma-desktop reaching 100% cpuload and also kmix reaching 80,90%.
So I was forced to kill -9 focuswriter and plasma-desktop.

Anyone having same issue?

This was focuswriter 1.3.1 from ubuntu ppa and stock kde 4.5.3 from maverick ppa.

Does this happen immediately or can you use it for a time before this happens?

I'm only asking because before this thread I hadn't even heard of the program but decided to give it a try. The OpenSUSE package works fine at any rate, and nothing is out of the ordinary. The only problem I've noticed is that the menu flickers when I need to use it, but that's about it.

I use exactly the same versions as you do too, with one exception: Maverick uses Qt 4.7 and I'm using Qt 4.6.3. but that's the only difference I can see.

As far as the kmix problem goes, have you tried disabling the typewriter sounds from within focuswriter?

Kryten2X4B wrote:Does this happen immediately or can you use it for a time before this happens?

..
As far as the kmix problem goes, have you tried disabling the typewriter sounds from within focuswriter?

Ok, I disabled the sound effects and now it runs flawlessy.
With typewriter sound enabled plasma-desktop and kmix reach full cpu occupation almost instantly.

Here it is a snipset of the strace output:

Code: Select all

poll([{fd=3, events=POLLIN}, {fd=8, events=POLLIN}, {fd=9, events=POLLIN}, {fd=7, events=POLLIN}], 4, 0) = 0 (Timeout)
read(7, 0x2659e84, 4096)                = -1 EAGAIN (Resource temporarily unavailable)
poll([{fd=7, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=7, revents=POLLOUT}])
writev(7, [{"(\3\4\0\273\0\0\0\2\0\240\7\372\6\340\0", 16}, {NULL, 0}, {"", 0}], 3) = 16
poll([{fd=7, events=POLLIN}], 1, -1)    = 1 ([{fd=7, revents=POLLIN}])
read(7, "\1\1\"r\0\0\0\0\0\0\0\0}\0\216\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0", 4096) = 32
read(7, 0x2659e84, 4096)                = -1 EAGAIN (Resource temporarily unavailable)
read(7, 0x2659e84, 4096)                = -1 EAGAIN (Resource temporarily unavailable)


After some time focuswriter package got an upgrade to version 1.3.2 so I decided to give it a second try.
Now things are more acceptable, anyway kmix still climbs up to 25% cpu after starting to type some text and slows down only after a few seconds from the last typed character.

So, now it appears usable but the problem lasts.
ciao

Do you use Pulseaudio by any chance? If you do, this explains this, as KMix shows a slider for each Pulseaudio application which is playing audio.

It is probable that focuswriter abusively connects and disconnects for each single key press it plays, thus causing KMix to have to create and destroy this slider for each key press made. In this case, it is a bug in focuswriter, which should keep it's connection to Pulseaudio open (which is probably better in terms of CPU usage in any case)

Yes, I do use pulseaudio, it's certainly focuswriter's fault.
Thanks for your reply