Clamp AudioParams with inputs to nominal range
The values of an AudioParam are supposed to be clamped to the nominal range. We do this already, but we forgot the case where there is a connection to the AudioParam. This can cause the values to go outside the nominal range and cause issues for the nodes that expected the values to be clamped appropriately. Manually tested ASAN build with this CL and crashes don't happen anymore. Without this, the crash was very reliable. Bug: 1015737, 1016165 Change-Id: Ia02bac7b60a7e20bdc5165dbfbb17df56d4d3171 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1869373 Commit-Queue: Raymond Toy <rtoy@chromium.org> Reviewed-by:Hongchan Choi <hongchan@chromium.org> Cr-Commit-Position: refs/heads/master@{#707818}
Showing
Please register or sign in to comment