Bug 182840 - high CPU usage after resume
Summary: high CPU usage after resume
Status: RESOLVED WORKSFORME
Alias: None
Product: kopete
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords: investigated, triaged
Depends on:
Blocks:
 
Reported: 2009-02-02 10:12 UTC by Marcus Better
Modified: 2018-10-21 05:10 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
strace of kopete during high CPU load (42.48 KB, text/plain)
2009-02-02 10:13 UTC, Marcus Better
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Marcus Better 2009-02-02 10:12:50 UTC
Version:           0.70.0 (using 4.2.00 (KDE 4.2.0), Debian packages)
Compiler:          cc
OS:                Linux (x86_64) release 2.6.28.1-melech

After resuming from suspend-to-RAM I noticed that kopete was draining the CPU. Otherwise the UI was responsive, but I'm not sure whether the network connection (Jabber) was re-established.

I have a single Jabber account configured, and it showed on-line status after the resume (but I don't trust that since it sometimes has problems reconnecting after resume).
Comment 1 Marcus Better 2009-02-02 10:13:51 UTC
Created attachment 30857 [details]
strace of kopete during high CPU load
Comment 2 Matt Rogers 2009-03-29 05:46:19 UTC
Can you provide a list of loaded plugins?
Comment 3 A. Spehr 2009-06-25 22:18:10 UTC
No response...
Comment 4 Andrew Crouthamel 2018-09-19 04:39:33 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Andrew Crouthamel 2018-10-21 05:10:57 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!