RESOLVED FIXED 281537
Ensure InitializeWebKit2 is called before allocating API::Features in WebPreferencesFeatures.cpp 
https://bugs.webkit.org/show_bug.cgi?id=281537
Summary Ensure InitializeWebKit2 is called before allocating API::Features in WebPref...
David Degazio
Reported 2024-10-15 17:20:35 PDT
It's possible to reach WebPreferencesFeatures::features() before initializing WebKit, for instance when initializing the SettingsMenu in awakeFromNib. We currently ensure WebKit is initialized before constructing any API object. But, before we can construct a Feature object, we need to first allocate a WTF::String, and we can do this before WTF::initialize() was called which can lead to issues. We should lazily initialize the feature list and ensure we have already initialized WebKit before beginning to construct the feature list.
Attachments
Add attachment proposed patch, testcase, etc.
Radar WebKit Bug Importer
Comment 1 2024-10-15 17:20:47 PDT
<rdar://problem/138003594>
David Degazio
Comment 2 2024-10-15 18:41:15 PDT
Pull request: https://github.com/WebKit/WebKit/pull/35253
EWS
Comment 3 2024-10-16 15:40:36 PDT
Committed 285293@main (ae4bc135bbb4): <https://commits.webkit.org/285293@main> Reviewed commits have been landed. Closing PR #35253 and removing active labels.
Note You need to log in before you can comment on or make changes to this bug.