Bug 188531

Summary:	busy wait for crash dialog
Product:	[Applications] drkonqi	Reporter:	Salvo "LtWorf" Tomaselli <tiposchi>
Component:	general	Assignee:	Unassigned bugs mailing-list <unassigned-bugs>
Status:	RESOLVED DUPLICATE
Severity:	normal
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Salvo "LtWorf" Tomaselli 2009-03-31 12:21:36 UTC

Version:           unknown (using 4.2.1 (KDE 4.2.1), Debian packages)
Compiler:          cc
OS:                Linux (i686) release 2.6.29-0.slh.1-sidux-686

The dialog that appears after a program crash does busy wait. If i don't click to close it, it will take 100% of one of my cores.

Comment 1 Andreas Pakulat 2009-03-31 12:56:48 UTC

Where in the code did you find that? Having a quick look I can't see any busy waits, however reading all the debug symbols into memory and creating a backtrace may indeed cause quite some cpu usage. But thats normal.

Comment 2 Pino Toscano 2009-03-31 14:25:37 UTC


*** This bug has been marked as a duplicate of bug 175362 ***

Comment 3 Salvo "LtWorf" Tomaselli 2009-03-31 19:04:55 UTC

Debug stuff takes a LIMITED amount of time. That uses 100% CPU until i close it.
I didn't look at the code but i am still able to recognize a busy wait when i meet one.