Bug 209130 - [GTK][WPE] fast/mediastream/change-tracks-media-stream-being-played.html is flaky crashing
Summary: [GTK][WPE] fast/mediastream/change-tracks-media-stream-being-played.html is f...
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: Tools / Tests (show other bugs)
Version: Other
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-03-15 18:32 PDT by Lauro Moura
Modified: 2023-01-25 20:43 PST (History)
1 user (show)

See Also:


Attachments
g_object_ref breakpoint from WPE release job 17281 (96.73 KB, text/plain)
2020-03-15 18:35 PDT, Lauro Moura
no flags Details
gst_gl_upload_transform_caps from WPE release job 17285 (92.91 KB, text/plain)
2020-03-15 18:36 PDT, Lauro Moura
no flags Details
g_type_check_instance_cast from WPE release build 17284 (58.19 KB, text/plain)
2020-03-15 18:37 PDT, Lauro Moura
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Lauro Moura 2020-03-15 18:32:16 PDT
Seems to be flaky crashing with 3 kinds of segfault (detailed backtraces in separate comments below):

* Getting a refcount of 0 inside g_object_ref deep inside GST
* Inside gst_gl_upload_transform_caps, also deep inside GST
* g_type_check_instance_cast segfault inside WebCore::WebKitMediaStreamTrackObserver::audioSamplesAvailable

Maybe related to bug194044?
Comment 1 Lauro Moura 2020-03-15 18:35:31 PDT
Created attachment 393630 [details]
g_object_ref breakpoint from WPE release job 17281
Comment 2 Lauro Moura 2020-03-15 18:36:44 PDT
Created attachment 393631 [details]
gst_gl_upload_transform_caps from WPE release job 17285
Comment 3 Lauro Moura 2020-03-15 18:37:21 PDT
Created attachment 393632 [details]
g_type_check_instance_cast from WPE release build 17284
Comment 4 Diego Pino 2023-01-25 20:43:39 PST
There are no references to this bug in any TestExpectations. It's probable this bug was solved at some point but it wasn't marked as closed. I'm closing this bug now. If you think this bug report is still valid, please reopen it and add an entry to TestExpectations.