Bug 73400 - artd crashes no discrenable cause
Summary: artd crashes no discrenable cause
Status: RESOLVED DUPLICATE of bug 73264
Alias: None
Product: arts
Classification: Miscellaneous
Component: artsd (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Stefan Westerfeld
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-01-24 13:24 UTC by eli
Modified: 2004-01-27 13:44 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description eli 2004-01-24 13:24:03 UTC 
Version:            (using KDE KDE 3.2.0)
Installed from:    Unlisted Binary Package
OS:          Linux

artd crashes occaisionally with no discrenable cause. Sorry about the lack of details. If there is anything that you can suggest to enable me to provide more details I will do my best to gather the information.
Comment 1 Stephan Kulow 2004-01-24 13:32:26 UTC 
a stack trace with --enable-debug? For now an arts bug is as likely as a memory fault in your RAM
Comment 2 eli 2004-01-24 14:27:48 UTC 
Then how come I get a dialog box that every once in awhile entitled

    Error - artsmessage

containing

   cpu overload, aborting

and I haven't done anything that I know of that would be producing any sound from the sound system.
Comment 3 eli 2004-01-24 18:41:19 UTC 
Just tried to delete some things from my home and /tmp directories.

From my home folder
/.kde/~cache*.local
/.kde/~socket*.local
/.kde/~tmp*.local
/.mcop
.ICEauthority
.Xauthority

From /tmp
/kde-eli
/ksocket-eli
/mc-eli
/mcop-eli
/orbit-eli
and a couple of other files that contained eli in the name.

I'll let you know in a couple of days if my problem has been resolved. If so, I will mark this report resolved on my own. Thanks
Comment 4 eli 2004-01-24 19:07:58 UTC 
OK... I think I found the culprit. When I had hardware detection on auto. CPU usage hovered around 50%. As soon as I specified the use alsa things went back down to normal.
Comment 5 Bernhard Rosenkraenzer 2004-01-27 13:44:07 UTC 

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