[Webkit-unassigned] [Bug 135365] New: Add an explicit way to initialize shared TextEncoding mappings besides accessing them.

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=135365

           Summary: Add an explicit way to initialize shared TextEncoding
                    mappings besides accessing them.
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: All
        OS/Version: All
            Status: NEW
          Keywords: InRadar
          Severity: Normal
          Priority: P2
         Component: WebCore Misc.
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: beidson at apple.com


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>

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.