Ubuntu
kopete package

kopete grabs all memory/CPU when triggered by unrelated file I/O

Bug #128537 reported by Andrew Kohlsmith
4
Affects Status Importance Assigned to Milestone
kopete (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: kopete

Kopete seems to have an issue where if there is some kind of file I/O (seemingly unrelated to Kopete), it starts grabbing all available memory and CPU. If Kontact is running, Kontact will join this race for hte top, and the OOM handler will generally end up killing Kontact. With Kontact closed down and not running at all, I have seen Kopete do this whenever archiving a web page inj Konqueror (any web page seems to do it), and even running the Adept package manager. I do not see these problems with Kopete shut down. Whether I have open chats or not does not matter. I am running MSN, Jabber and ICQ plugins with Kopete.

When Kopete does start this grab for memory and CPU, it will calm itself down in about 1-2 minutes and my system will become usable again.

This system has a gig of memory, half a gig of swap, and is running the VESA Xorg driver (ATI video), if that matters.

While I do not have concrete evidence of this, I believe that this was also occurring with the "official" KDE 3.5.6 Kubuntu packages, which is why I tried updating to the packages offered by Jonathan Riddell.

Revision history for this message
Andrew Kohlsmith (akohlsmith-kubuntu) wrote :

I figured out the trigger.

Kopete will grab all CPU/mem (and race Kontact to OOM kill if it's running) if any KDE application opens a file selection dialog (e.g. save as or open).

It is 100% repeatable.

Revision history for this message
Andrew Kohlsmith (akohlsmith-kubuntu) wrote :

It may need an ongoing MSN conversation to trigger...

i.e.
1) open up kopete, start up an MSN conversation and get a decent conversation going
2) click on a link in konq or archive a web page.

Kopete starts ratcheting up mem and CPU.

Revision history for this message
Andrew Kohlsmith (akohlsmith-kubuntu) wrote :

Homing in on this bug...

1) Kopete does not need to be online. The MSN conversation bit in my last note was a red herring.
2) Save As doesn't always cause it, but Konq's archive web page tool does.

Revision history for this message
Andrew Kohlsmith (akohlsmith-kubuntu) wrote :

Just another datapoint... it isn't *just* a file dialogue that trips this, but that is the only easily-reproducible method I've come across.

Revision history for this message
Jonathan Riddell (jr) wrote :

I can't recreate this and neither can Hobbsee. Possibly an issue in feisty backports or dependent on your setup. Running kopete through valgrind may well be the way to go.

Revision history for this message
Jonathan Riddell (jr) wrote :

Also does it effect a newly created user on your system?

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in kopete:
status: New → Invalid
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Oh, it'd also be worthwhile to check if this still happens in Intrepid before reopening.

Revision history for this message
Julian Edwards (julian-edwards) wrote :

FWIW this is happening to me (at least Ithink it's the same bug) in oneiric and precise. At startup it eats CPU - it's not the statistics plugin problem as I don't have that enabled.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.