Bug 558981 - latest pulseaudio update cause 100% CPU
Summary: latest pulseaudio update cause 100% CPU
Keywords:
Status: CLOSED DUPLICATE of bug 559467
Alias: None
Product: Fedora
Classification: Fedora
Component: pulseaudio
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Lennart Poettering
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-01-26 20:06 UTC by Jeff Guerdat
Modified: 2010-02-12 15:06 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-02-12 15:06:53 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Jeff Guerdat 2010-01-26 20:06:20 UTC
Description of problem:

Installed the latest pulseaudio updates (0.9.21-4.fc12.i686) with other updates.  Rebooted and logged in.  Ran Thunderbird for mail.  New mail sound (a .wav file) plays about .1 second and then pulseaudio goes to 100% CPU utilization.  Playing the .wav in VLC or mplayer doesn't cause an issue nor does any other sound that I've tried.


Version-Release number of selected component (if applicable):

0.9.21-4.fc12.i686

How reproducible:

Always when playing new mail sound in T'bird.

Steps to Reproduce:
1.Run Thunderbird
2.Check mail
3.New mail causes sound to play and CPU to go to 100% till pulseaudio is killed
  
Actual results:

pulseaudio uses 100% CPU

Expected results:

low utilization

Additional info:

Backdating pulseaudio to 0.9.19-2.fc12.i686 cures problem

Comment 1 Lennart Poettering 2010-01-28 03:14:36 UTC
Is there any output in syslog from PA? Please attach.

Comment 2 Jeff Guerdat 2010-01-28 13:33:49 UTC
Absolutely nothing noted until pulseaudio restarts after having been killed:

Jan 28 08:18:27 toshiba rtkit-daemon[1838]: Sucessfully made thread 2678 of process 2678 (/usr/bin/pulseaudio) owned by '500' high priority at nice level -11.
Jan 28 08:18:28 toshiba rtkit-daemon[1838]: Sucessfully made thread 2694 of process 2678 (/usr/bin/pulseaudio) owned by '500' RT at priority 5.
Jan 28 08:18:28 toshiba rtkit-daemon[1838]: Sucessfully made thread 2695 of process 2678 (/usr/bin/pulseaudio) owned by '500' RT at priority 5.
Jan 28 08:18:28 toshiba rtkit-daemon[1838]: Sucessfully made thread 2697 of process 2697 (/usr/bin/pulseaudio) owned by '500' high priority at nice level -11.
Jan 28 08:18:28 toshiba pulseaudio[2697]: pid.c: Daemon already running.
Jan 28 08:18:28 toshiba rtkit-daemon[1838]: Sucessfully made thread 2698 of process 2698 (/usr/bin/pulseaudio) owned by '500' high priority at nice level -11.
Jan 28 08:18:28 toshiba pulseaudio[2698]: pid.c: Daemon already running.
Jan 28 08:18:28 toshiba rtkit-daemon[1838]: Sucessfully made thread 2699 of process 2699 (/usr/bin/pulseaudio) owned by '500' high priority at nice level -11.
Jan 28 08:18:28 toshiba pulseaudio[2699]: pid.c: Daemon already running.
Jan 28 08:18:28 toshiba rtkit-daemon[1838]: Sucessfully made thread 2700 of process 2700 (/usr/bin/pulseaudio) owned by '500' high priority at nice level -11.
Jan 28 08:18:28 toshiba pulseaudio[2700]: pid.c: Daemon already running.
Jan 28 08:18:28 toshiba rtkit-daemon[1838]: Sucessfully made thread 2701 of process 2701 (/usr/bin/pulseaudio) owned by '500' high priority at nice level -11.
Jan 28 08:18:28 toshiba pulseaudio[2701]: pid.c: Daemon already running.
Jan 28 08:18:28 toshiba rtkit-daemon[1838]: Sucessfully made thread 2702 of process 2702 (/usr/bin/pulseaudio) owned by '500' high priority at nice level -11.
Jan 28 08:18:28 toshiba pulseaudio[2702]: pid.c: Daemon already running.

Comment 3 FC12-user 2010-01-28 19:14:53 UTC
I experience the exact same problem since the last pulseaudio update.

Comment 4 Glenn Zazulia 2010-01-31 23:19:19 UTC
Same here -- same PA version & (mis-)behavior, and nothing to note in syslog.

Comment 5 brendan 2010-02-01 19:46:24 UTC
I can confirm the same behavior on x86_64.  Totally up to date F12.

Comment 6 Lennart Poettering 2010-02-12 15:06:53 UTC

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


Note You need to log in before you can comment on or make changes to this bug.