After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 412951 - [PATCH] esound takes up 100% of the CPU after client disconnect
[PATCH] esound takes up 100% of the CPU after client disconnect
Status: RESOLVED FIXED
Product: esound
Classification: Deprecated
Component: general
0.2.x
Other All
: Normal critical
: ---
Assigned To: Esound Maintainers
Esound Maintainers
: 414053 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-02-28 05:33 UTC by Joe Marcus Clarke
Modified: 2007-03-03 07:06 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Attachments
Fix CPU consumption problem (692 bytes, patch)
2007-02-28 05:33 UTC, Joe Marcus Clarke
none Details | Review

Description Joe Marcus Clarke 2007-02-28 05:33:24 UTC
Please describe the problem:
The changes in esound 0.2.37 introduce a nasty bug in which esd will start to spin rapidly in a read/select/accept loop taking up 100% of the CPU until it is killed.  The problem stems from the fact that EOF is no longer properly detected on the player socket.  The attached patch corrects the problem simply by making sure we return on EOF instead of breaking out of the inner do/while loop.

Steps to reproduce:
1. Start esd
2. Run a test pattern using the Sound capplet
3. Stop the test pattern


Actual results:
esd will start to clime in CPU usage very rapidly after the test pattern completes.

Expected results:
esd should go to sleep

Does this happen every time?
yes

Other information:
Comment 1 Joe Marcus Clarke 2007-02-28 05:33:56 UTC
Created attachment 83520 [details] [review]
Fix CPU consumption problem
Comment 2 David Schleef 2007-03-02 23:13:08 UTC
*** Bug 414053 has been marked as a duplicate of this bug. ***
Comment 3 David Schleef 2007-03-03 07:06:06 UTC
Applied, thanks.