Open
Bug 1404985
Opened 7 years ago
Updated 2 years ago
Remove locking from MediaEngineWebRTC*
Categories
(Core :: WebRTC: Audio/Video, enhancement, P3)
Core
WebRTC: Audio/Video
Tracking
()
NEW
People
(Reporter: padenot, Unassigned)
References
(Blocks 1 open bug)
Details
We have evidence this is an issue: we’re able to load the MSG much higher when using the Web Audio API without a MediaStream from getUserMedia. Lock contention profiling has been broken on a stock macbook pro (because of MacOS System Integrity Protection, that broke a bunch of dtrace probes), we have to use Linux or something to profile this. On Windows, when profiling, I see that in the locking stack, there is a symbol that hints at the fact that the mutex is known to have non-trivial contention (it’s a symbol like LockInternalSlowPath or something), which means it’s not using fast spinlocks or similar techniques to enforce linearity.
Reporter | ||
Comment 1•7 years ago
|
||
This is the bug where we remove the locks from our code. It's still going to lock in the APM function, this is going to be handled in bug 1404962.
Rank: 20
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•