25040 2009-04-03 15:32:22 -0700 Make SecurityOrigin thread safe. 2023-03-27 08:46:51 -0700 1 1 1 Unclassified WebKit WebCore Misc. 528+ (Nightly build) All All RESOLVED WONTFIX P2 Normal --- 24492 0 jianli webkit-unassigned annevk ap dimich egyptnz27 fishd jam levin oldest_to_newest 116498 0 jianli 2009-04-03 15:32:22 -0700 We need to make SecurityOrigin thread safe, i.e., the way to initialize static values in SecurityOrigin and other classes it calls. Considering moving all statics into one place and use TLS. Currently we assume that main thread will initialize a document and thus create a SecurityOrigin before any other thread that uses WebKit is run. 116501 1 fishd 2009-04-03 15:53:38 -0700 I don't think TLS is a good answer. What if someone modifies these tables lazily? 116528 2 ap 2009-04-04 02:21:27 -0700 Yes, I do not see how TLS would be relevant here. What we really need is to move SecurityOrigin checks out of XMLHttpRequest and into DocumentThreadableLoader. 125736 3 fishd 2009-06-13 22:31:45 -0700 > What we really need is to move SecurityOrigin checks out of XMLHttpRequest and > into DocumentThreadableLoader. So that makes this bug WONTFIX right? The implication being that SecurityOrigin checks will then only run on the WebKit main thread. 1944253 4 annevk 2023-03-27 08:46:51 -0700 Resolving as WONTFIX per comment 3 and due to general inactivity.