Add process lock when setting looping, loop start, and loop end
The audio thread reads the looping parameters (looping, start, and end) possibly many times while rendering the data. The main thread can modify any of these at any time. This is a race. To eliminate the race, modify the setters for looping, loop start, and loop end to add a mutex for the process lock so that the main thread can't modify these until audio thread is finished processing. Bug: 1107500 Change-Id: Ied5cfb35cfb91e7982dc68e694dead09b1c74aa2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2306555 Commit-Queue: Raymond Toy <rtoy@chromium.org> Reviewed-by:Hongchan Choi <hongchan@chromium.org> Cr-Commit-Position: refs/heads/master@{#791825}
Showing
Please register or sign in to comment