Bug 219243

Summary: REGRESSION(r270158) [GStreamer] allocator crashes after this revision
Product: WebKit Reporter: Lauro Moura <lmoura>
Component: WebKit Misc.Assignee: Nobody <webkit-unassigned>
Status: RESOLVED MOVED    
Severity: Normal CC: bugs-noreply, pnormand
Priority: P2    
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
fast/storage/serialized-script-value.html crash log none

Lauro Moura
Reported 2020-11-22 04:00:23 PST
Created attachment 414786 [details] fast/storage/serialized-script-value.html crash log After r270158, running a large number of tests may lead to a GStreamer gst_allocator_alloc crash. This currently happening to fast/storage/serialized-script-value.html [1] on the release bots (crash log attached). Trying to reproduce it locally, currently the best thing I managed to do was running all fast/ tests, causing the same crashlog on different tests once each run. But one thing in common was the speechrecognition tests being run in the crashing worker right before the test that crashed. [1] https://results.webkit.org/?suite=layout-tests&test=fast%2Fstorage%2Fserialized-script-value.html
Attachments
fast/storage/serialized-script-value.html crash log (43.40 KB, text/plain)
2020-11-22 04:00 PST, Lauro Moura 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Philippe Normand
Comment 1 2020-11-22 05:03:33 PST
It's better to skip all webspeech related tests for now, instead of random unrelated tests failing due to webspeech.
Philippe Normand
Comment 2 2020-11-22 05:12:27 PST
https://trac.webkit.org/r270162
Lauro Moura
Comment 3 2020-11-22 07:56:48 PST
(In reply to Philippe Normand from comment #1) > It's better to skip all webspeech related tests for now, instead of random > unrelated tests failing due to webspeech. Yeah. It could end up being one of those neverending test list (like the xcb sequence and mesa ones).
Philippe Normand
Comment 4 2021-03-28 03:55:50 PDT
As per comment 1
Note You need to log in before you can comment on or make changes to this bug.