By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.
Bug 2346 - soundserver repeatedly crashing
Summary: soundserver repeatedly crashing
Status: NEEDINFO
Alias: None
Product: TDE
Classification: Unclassified
Component: tdebase (show other bugs)
Version: R14.0.x [Trinity]
Hardware: Other Linux
: P5 normal
Assignee: Timothy Pearson
URL:
Depends on:
Blocks:
 
Reported: 2015-02-05 08:12 CST by Kristopher
Modified: 2018-08-02 21:05 CDT (History)
2 users (show)

See Also:
Compiler Version:
TDE Version String:
Application Version:
Application Name:

Attachments
Backtrace from TDE Crash Handler (8.21 KB, text/plain)
2015-02-05 08:12 CST, Kristopher 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Kristopher 2015-02-05 08:12:44 CST 
Created attachment 2446 [details]
Backtrace from TDE Crash Handler

Today, for no apparently reason, artsd started repeatedly crashing for no apparently reason. I haven't done any upgrades on this machine or swapped out any hardware/software or changed any settings since the last time it worked (which was yesterday), so this crash is *not* caused by anything on my end.

This crash is so pervasive that TDE can't even log out correctly due to the sheer volume of TDE Crash Handler windows that keep opening -- just in the three minutes it took for me to get here and type this report, I've gotten 100 TDE Crash Handler windows just for the sound server! I have to switch to a VT and manually restart TDM to get out of TDE.

I have attached a backtrace from the TDE Crash Handler, and I've censored user/server information.
Comment 1 Michele Calgaro 2018-08-02 21:05:06 CDT 
Kris,
there were some problems on the sound server that have been fixed in R14.0.5. Can you test again when R14.0.5 is out and let us know if this problem is still valid?