[Webkit-unassigned] [Bug 233488] New: make font code usable from multiple threads
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Wed Nov 24 23:10:34 PST 2021
https://bugs.webkit.org/show_bug.cgi?id=233488
Bug ID: 233488
Summary: make font code usable from multiple threads
Product: WebKit
Version: WebKit Local Build
Hardware: Unspecified
OS: Unspecified
Status: NEW
Severity: Normal
Priority: P2
Component: Layout and Rendering
Assignee: webkit-unassigned at lists.webkit.org
Reporter: heycam at apple.com
CC: bfulgham at webkit.org, clord at igalia.com,
mmaxfield at apple.com, simon.fraser at apple.com,
zalan at apple.com
OffscreenCanvas needs the ability to call into font code from worker threads. Bug 219283 was filed to make FontCache and FontCascadeCache thread-safe, but I'm planning to take the approach of giving each worker thread (that needs it) its own FontCache object. Rather than sharing font objects between threads, each thread will create and use completely independent font objects. This will mean having all font-related caches exist for each thread, and I plan to handle that by hanging them off FontCache. There are also a bunch of static variables with initializers in font code, which in the presence of -fno-threadsafe-statics, either need to be non-static, have locking around them, or be made thread-specific by being moved onto FontCache.
I have a bunch of small patches to address the issues I've found so far, which I'll file blocking this bug.
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20211125/b991886c/attachment.htm>
More information about the webkit-unassigned
mailing list