New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 680117 link

Starred by 1 user
Status: Archived
Owner: ----
Closed: May 2018
Cc:
█ brajkumar@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Chrome doesn't free pulseaudio resources after stopping playing audio from the microphone

Reported by m.zd...@gmail.com, Jan 11 2017 
UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36

Steps to reproduce the problem:
Just run the testcase on eg. jsfiddle.net.

What is the expected behavior?
After playback is paused, element removed from DOM, tracks stopped Chrome should free pulseaudio resource.

What went wrong?
After the test finishes and settles down, pulseaudio still eats pretty much of the CPU (almost 100% of the single core)  until you close the page.

During the CPU load "pacmd list-clients | grep Chrome | wc -l" prints 54.

Did this work before? N/A 

Does this work in other browsers? N/A

Chrome version: 55.0.2883.87  Channel: stable
OS Version: Linux myhost 4.6.0-1-amd64 #1 SMP Debian 4.6.4-1 (2016-07-18) x86_64 GNU/Linux
Flash Version: Shockwave Flash 24.0 r0
testcase.js
480 bytes View Download

Comment 1 by brajkumar@chromium.org, Jan 12 2017

Cc: brajkumar@chromium.org
Labels: Needs-Feedback
Reporter@ Thanks for filing this issue, Could you please provide a sample test case of the issue in a jsfiddle to check it from chrome-TE end.

Thanks!

Comment 2 by m.zd...@gmail.com, Jan 12 2017 

No problem. I've just placed the content of the attached file to jsfiddle: https://jsfiddle.net/1gr0nwkw/

Comment 3 by ajha@chromium.org, Jan 16 2017

Labels: Needs-Triage-M55
Project Member

Comment 4 by sheriffbot@chromium.org, Jan 23 2017

Labels: -Needs-Feedback Needs-Review
Owner: brajkumar@chromium.org
Thank you for providing more feedback. Adding requester "brajkumar@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 5 by cda...@chromium.org, Mar 13 2017 

Cleaning up "Needs-Review" label as we are not using this label for triage. Ref  bug 684919

Comment 6 by cda...@chromium.org, Mar 13 2017

Labels: -Needs-Review

Comment 7 by brajkumar@chromium.org, May 12 2017

Labels: Needs-Feedback
Owner: ----
Could you please confirm what's the expected behavior for this issue? Tested this issue on Ubuntu 14.04 using chrome latest stable #58.0.3029.110, By clicking on run from the provided test case file from comment #2 observed some audio playing for a second and stopped abruptly. By checking the same on Firfox browser observed no audio.

Comment 8 by m.zd...@gmail.com, May 12 2017 

The testcase is only for Chrome. It sould play one second sound from your microphone and then stop. Afterwards pulseaudio settles at high CPU usage (in my case it is above 50% when checked with htop command). If you later close the jsfiddle tab then CPU of the pulseaudio process goes back to normal.

Tested now with Chrome 58.0.3029.81 (64-bit)
Project Member

Comment 9 by sheriffbot@chromium.org, May 12 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "brajkumar@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Project Member

Comment 10 by sheriffbot@chromium.org, May 14 2018

Status: Archived (was: Unconfirmed)
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 11 by m.zd...@gmail.com, May 14 2018 

How can I reopen the bug? It is still a valid issue, reproducible in Version 66.0.3359.139 (Official Build) (64-bit).
►

Sign in to add a comment