WebKit Bugzilla
New
Browse
Search+
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
NEW
135365
Add an explicit way to initialize shared TextEncoding mappings besides accessing them.
https://bugs.webkit.org/show_bug.cgi?id=135365
Summary
Add an explicit way to initialize shared TextEncoding mappings besides access...
Brady Eidson
Reported
2014-07-28 16:11:30 PDT
Add an explicit way to initialize shared TextEncoding mappings besides accessing them. In a few places in code we know UTF8Encoding() will be accessed on a background thread, possibly before the text encoding maps are ever set up on the main thread. We "fix" this by accessing the UTF8Encoding() on the main thread before the background thread gets going. See LocalStorageDatabaseTracker::LocalStorageDatabaseTracker in WK2 for example. That's only for one encoding. We should have an explicit, obvious way of initializing all the common TextEncodings from the main thread when this comes up. <
rdar://problem/9127819
>
Attachments
Add attachment
proposed patch, testcase, etc.
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug