Bug 200896 - Move call to initializeMainThread introduced in r248549 to after WebKit.framework has been loaded
Summary: Move call to initializeMainThread introduced in r248549 to after WebKit.frame...
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: New Bugs (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Alex Christensen
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2019-08-19 13:43 PDT by Alex Christensen
Modified: 2019-08-21 15:32 PDT (History)
4 users (show)

See Also:

Attachments
Patch (4.80 KB, patch)
2019-08-19 13:47 PDT, Alex Christensen 		no flags Details | Formatted Diff | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Alex Christensen 2019-08-19 13:43:25 PDT 
Move call to initializeMainThread introduced in r248549 to after WebKit.framework has been loaded
Comment 1 Alex Christensen 2019-08-19 13:47:46 PDT 
Created attachment 376707 [details]
Patch
Comment 2 Alex Christensen 2019-08-19 13:47:49 PDT 
<rdar://problem/54479065>
Comment 3 Alex Christensen 2019-08-19 13:56:26 PDT 
http://trac.webkit.org/r248862
Comment 4 mitz 2019-08-19 14:33:18 PDT 
(In reply to Alex Christensen from comment #2)
> <rdar://problem/54479065>

This doesn’t fix that Radar. The Radar is caused by the fact that the services are no longer being signed with the library validation flag when they should be, and that was caused by r248164.
Comment 5 mitz 2019-08-21 15:31:10 PDT 
(In reply to Alex Christensen from comment #3)
> http://trac.webkit.org/r248862

Should this change be reverted?
Comment 6 Chris Dumez 2019-08-21 15:32:50 PDT 
This did not do anything and is more code so I think so. Alex, do you agree?