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

Issue 718417 link

Starred by 1 user
Status: Assigned
Owner:
grunell@chromium.org
Cc:
tommi@chromium.org
ossu@chromium.org
█ tlegrand@chromium.org
dalecur...@chromium.org
solenberg@chromium.org
█ olka@chromium.org
maxmorin@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Chrome
Pri: 3
Type: Feature



Sign in to add a comment

Check if the audio thread is run or can be run on realtime prio on Linux and ChromeOS

Project Member Reported by grunell@chromium.org, May 4 2017 
This came up in https://bugs.chromium.org/p/chromium/issues/detail?id=710245#c94 (comments 94-99):

Since https://crrev.com/7b97c3240fb3da0826f244f9b592fc1761fb6554 render thread priorities are allowed to be set on Linux and ChromeOS. The audio thread is set to base::ThreadPriority::REALTIME_AUDIO prio [1], but it's not clear if it takes effect.

1. Check if the audio thread runs on realtime prio.
2. If not, what can we do to make it so?

[1] https://cs.chromium.org/chromium/src/media/audio/audio_device_thread.cc?l=51

Comment 1 by maxmorin@chromium.org, May 4 2017 

Changing niceness on Linux requires CAP_SYS_NICE capabilities http://man7.org/linux/man-pages/man2/setpriority.2.html. Ordinary users doesn't usually have this, so I don't think there's a way for us to lower out niceness on Linux. Maybe ChromeOS is different? How about other platforms?

Comment 2 by cychiang@chromium.org, May 4 2017 

The realtime priority of audio thread on browser process is fixed in
https://chromium-review.googlesource.com/c/456979/
So I think chrome has the capability to change rt priority and nice values.
maxmorin via monorail <monorail+v2.3787522839@chromium.org>於 2017年5月4日
週四，下午9:27寫道：
►

Sign in to add a comment