Bug 291370

Summary: KDE crashes or locks up
Product: [I don't know] kde Reporter: opis <jklava>
Component: generalAssignee: Unassigned bugs mailing-list <unassigned-bugs>
Status: RESOLVED WORKSFORME    
Severity: major CC: cfeck
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Unlisted Binaries   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description opis 2012-01-12 13:50:18 UTC 
Version:           unspecified (using KDE 4.6.0) 
OS:                Linux

KDE crashes or locks up after completing boot or any time thereafter. No user action needed.




I am running opensuse 11.4 on a HP Pavilion dv6 with i7-26xx CPU, Radeon 6xxx GPU, lots of ram

The only clue as to what happens is that xosview shows one of the CPUs in a race or loop condition, ie 100% CPU utilization and the fan runs at max rpms.

I tried to upgrade to opensuse 12.1 but that was even worse. Kontact, Konqueror and other apps just simply crashed to the point where using the system was not an option.



Reproducible: Always

Steps to Reproduce:
Just start KDE and play Shisen-Sho, The worst offending application in this respect is Shisen-Sho. Playing the game is a guaranteed way to lock up KDE.

Actual Results:  
When the system locks up, the only way to recover is to hold down the power switch, losing most work. 


Expected Results:  
It should not lock up, right?

When the system locks up, the only way to recover is to hold down the power switch, losing most work. 

I am running opensuse 11.4 on a HP Pavilion dv6 with i7-26xx CPU, Radeon 6xxx GPU, lots of ram

The only clue as to what happens is that xosview shows one of the CPUs in a race or loop condition, ie 100% CPU utilization and the fan runs at max rpms.

I tried to upgrade to opensuse 12.1 but that was even worse. Kontact, Konqueror and other apps just simply crashed to the point where using the system was not an option.
Comment 1 Christoph Feck 2012-01-12 15:23:49 UTC 
Can you check which process uses 100% CPU?

(Use Ctrl+Esc to show the process monitor)
Comment 2 Christoph Feck 2013-01-12 03:19:22 UTC 
If you can provide the information requested in comment #1, please add it.
Comment 3 opis 2013-01-14 11:18:45 UTC 
On Saturday, January 12, 2013 03:19:22 AM you wrote:
> https://bugs.kde.org/show_bug.cgi?id=291370
> 
> Christoph Feck <christoph@maxiom.de> changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
> Status|UNCONFIRMED                 |NEEDSINFO
>          Resolution|---                         |WAITINGFORINFO
> 
> --- Comment #2 from Christoph Feck <christoph@maxiom.de> ---
> If you can provide the information requested in comment #1, please add it.


Problem seems to be solved, not having any more Kontact crashes.