RESOLVED FIXED 213637
Initializing the main thread should initialize the main run loop
https://bugs.webkit.org/show_bug.cgi?id=213637
Summary Initializing the main thread should initialize the main run loop
Geoffrey Garen
Reported 2020-06-25 21:16:31 PDT
Initializing the main thread should initialize the main run loop
Attachments
Patch (23.57 KB, patch)
2020-06-25 21:35 PDT, Geoffrey Garen
no flags
Patch (33.78 KB, patch)
2020-06-26 07:35 PDT, Geoffrey Garen
no flags
Patch (34.93 KB, patch)
2020-06-26 10:38 PDT, Geoffrey Garen
no flags
Geoffrey Garen
Comment 1 2020-06-25 21:35:33 PDT
Geoffrey Garen
Comment 2 2020-06-26 07:35:03 PDT
Darin Adler
Comment 3 2020-06-26 09:33:15 PDT
Comment on attachment 402862 [details] Patch EWS failures *do* look like they are caused by the changes in the patch.
Geoffrey Garen
Comment 4 2020-06-26 09:52:38 PDT
Looks like I need to update WebKitTestRunner and DumpRenderTree. Oops!
Geoffrey Garen
Comment 5 2020-06-26 10:38:21 PDT
Saam Barati
Comment 6 2020-06-26 12:20:42 PDT
Comment on attachment 402880 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=402880&action=review > Source/WTF/ChangeLog:8 > + Previously, some code initialized one, some the other, and some both; what's "one" and "other" here?
Geoffrey Garen
Comment 7 2020-06-26 12:23:36 PDT
(In reply to Saam Barati from comment #6) > Comment on attachment 402880 [details] > Patch > > View in context: > https://bugs.webkit.org/attachment.cgi?id=402880&action=review > > > Source/WTF/ChangeLog:8 > > + Previously, some code initialized one, some the other, and some both; > > what's "one" and "other" here? WTF::initializeMainThread() and WTF::RunLoop::initializeMain().
EWS
Comment 8 2020-06-26 12:28:22 PDT
Committed r263575: <https://trac.webkit.org/changeset/263575> All reviewed patches have been landed. Closing bug and clearing flags on attachment 402880 [details].
Radar WebKit Bug Importer
Comment 9 2020-06-26 12:29:18 PDT
Radar WebKit Bug Importer
Comment 10 2020-06-26 12:29:22 PDT
Note You need to log in before you can comment on or make changes to this bug.