| Summary: | Make WebLocalizedString() thread-safe | ||||||
|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | Chris Dumez <cdumez> | ||||
| Component: | WebCore Misc. | Assignee: | Chris Dumez <cdumez> | ||||
| Status: | RESOLVED FIXED | ||||||
| Severity: | Normal | CC: | achristensen, darin, ggaren, sam, simon.fraser, thorton, webkit-bug-importer, wenson_hsieh | ||||
| Priority: | P2 | Keywords: | InRadar | ||||
| Version: | WebKit Nightly Build | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Attachments: |
|
||||||
|
Description
Chris Dumez
2021-09-29 07:54:22 PDT
Created attachment 439607 [details]
Patch
Comment on attachment 439607 [details]
Patch
Seems like a bad idea to me. This assertion caught thread safety bug in important clients several times in recent memory.
One could claim that we shouldn't care because those re client bugs not WebKit ones; I will not agree with that.
Comment on attachment 439607 [details]
Patch
I've been told that all those recent instances were not real bugs, and it was OK to call WebLocalizedString on background threads then. So r+.
Committed r283225 (242267@main): <https://commits.webkit.org/242267@main> All reviewed patches have been landed. Closing bug and clearing flags on attachment 439607 [details]. |