Do not access other Oilpan-managed object in class destructors in modules/webaudio |
||||
Issue descriptionhttps://test-results.appspot.com/dashboards/flakiness_dashboard.html#testType=webkit_layout_tests%20(with%20patch)&showAllRuns=true&tests=webaudio%2Finternals%2Faudiosource-premature-gc.html We do not know when this started, but it seems like flaky in rare cases. We should suppress the flakiness and handle it later.
,
Nov 29 2017
,
Nov 29 2017
Note: this doesn't crash on browser or content_shell.
,
Nov 29 2017
My local verification was based on the CL https://chromium-review.googlesource.com/c/chromium/src/+/779862, but it does not crash on ToT. Please ignore #1 and #3. I am also lowering the priority to 3.
,
Nov 29 2017
With the iteration = 100, the test passes on Mac and Linux.
,
Dec 1 2017
I change the title to track the bigger issue in WebAudio. haraken@ pointed out the destruction process in BaseAudioContext is incorrect from Oilpan-GC perspective: https://chromium-review.googlesource.com/c/chromium/src/+/779862#message-3b8e3ea8e9c6c7d04a5fe7edfcc4d3e4ff899e4f We have to assess all class destructors in module/webaudio to find out if it accesses other Oilpan-managed objects. |
||||
►
Sign in to add a comment |
||||
Comment 1 by hongchan@chromium.org
, Nov 29 2017