Bug 25040

Summary:	Make SecurityOrigin thread safe.
Product:	WebKit	Reporter:	Jian Li <jianli>
Component:	WebCore Misc.	Assignee:	Nobody <webkit-unassigned>
Status:	RESOLVED WONTFIX
Severity:	Normal	CC:	annevk, ap, dimich, egyptnz27, fishd, jam, levin
Priority:	P2
Version:	528+ (Nightly build)
Hardware:	All
OS:	All
Bug Depends on:	24492
Bug Blocks:

Description Jian Li 2009-04-03 15:32:22 PDT

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.

Comment 1 Darin Fisher (:fishd, Google) 2009-04-03 15:53:38 PDT

I don't think TLS is a good answer.  What if someone modifies these tables lazily?

Comment 2 Alexey Proskuryakov 2009-04-04 02:21:27 PDT

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.

Comment 3 Darin Fisher (:fishd, Google) 2009-06-13 22:31:45 PDT

> 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.

Comment 4 Anne van Kesteren 2023-03-27 08:46:51 PDT

Resolving as WONTFIX per comment 3 and due to general inactivity.