Check WorkletPendingTasks when BaseAudioContext is going away
This is a speculative fix for the bug associated. The following is the
scenario of potential NULL-deference:
1. BaseAudioContext.audioWorklet.addModule('some.url');
2. BaseAudioContext is destroyed.
3. The callback originated from the module loading arrives, but the
associated context is already gone.
4. Crash with NULL deference, because the callback touches the
destination node of the AudioContext.
This CL fixes the issue by keeping track of WorkletPendingTasks until
module loading tasks are resolved.
Bug: 839642
Change-Id: I154bb8c56f0fa95d6708c642047c7b05acf83eb2
Reviewed-on: https://chromium-review.googlesource.com/1062795Reviewed-by:
Raymond Toy <rtoy@chromium.org>
Reviewed-by:
Kentaro Hara <haraken@chromium.org>
Reviewed-by:
Hiroki Nakagawa <nhiroki@chromium.org>
Commit-Queue: Hongchan Choi <hongchan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#560290}
Showing
Please register or sign in to comment