After resuming from suspend, either RAM or Disk sometimes konqueror uses 100% of one CPU forever. Debugging the issue I realized that this always happens if I left any google search open, closing the offending tab reduces the CPU load back to normal. The issue seems similar to bug #162767 and #218047.
(In reply to comment #0) > After resuming from suspend, either RAM or Disk sometimes konqueror uses > 100% of one CPU forever. > > Debugging the issue I realized that this always happens if I left any google > search open, closing the offending tab reduces the CPU load back to normal. > The issue seems similar to bug #162767 and #218047. Which browser engine ? khtml or kwebkitpart (Settings->Configure Konqueror->General->Default browser engine) ? Or does that not matter ?
Hello. I'm using KHTML, in fact I don't even have kwebkitpart. I'll try to find the time to install and test with it. BR René On Monday 16 April 2012 06:08:56 Dawit Alemayehu wrote: > https://bugs.kde.org/show_bug.cgi?id=296859 > > Dawit Alemayehu <adawit@kde.org> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |adawit@kde.org > > --- Comment #1 from Dawit Alemayehu <adawit@kde.org> --- > (In reply to comment #0) > > > After resuming from suspend, either RAM or Disk sometimes konqueror uses > > 100% of one CPU forever. > > > > Debugging the issue I realized that this always happens if I left any > > google search open, closing the offending tab reduces the CPU load back > > to normal. The issue seems similar to bug #162767 and #218047. > > Which browser engine ? khtml or kwebkitpart (Settings->Configure > Konqueror->General->Default browser engine) ? Or does that not matter ?
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone!
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
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!
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!