Use the DatabaseTracker only on the FILE thread.

Use the DatabaseTracker only on the FILE thread.

TEST=none
BUG=81916
Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=86030

[michaeln, 2011-05-19 20:18:33]

please take a look

[jochen (gone - plz use gerrit), 2011-05-19 20:44:47]

On 2011/05/19 20:18:33, michaeln wrote:
> please take a look

See http://crbug.com/74433 - I think we must not invoke WebSecurityOrigin
methods on the FILE thread

[michaeln, 2011-05-19 20:48:49]

On 2011/05/19 20:44:47, jochen wrote:
> On 2011/05/19 20:18:33, michaeln wrote:
> > please take a look
> 
> See http://crbug.com/74433 - I think we must not invoke WebSecurityOrigin
> methods on the FILE thread

I know we must not invoke the DatabaseTracker on the WEBKIT thread.

SecurityOrigin is used on background threads within WebCore too. If there are
race conditions with it's initialization, we should fix it initialization.

[jochen (gone - plz use gerrit), 2011-05-19 21:11:45]

On 2011/05/19 20:48:49, michaeln wrote:
> On 2011/05/19 20:44:47, jochen wrote:
> > On 2011/05/19 20:18:33, michaeln wrote:
> > > please take a look
> > 
> > See http://crbug.com/74433 - I think we must not invoke WebSecurityOrigin
> > methods on the FILE thread
> 
> I know we must not invoke the DatabaseTracker on the WEBKIT thread.
> 
> SecurityOrigin is used on background threads within WebCore too. If there are
> race conditions with it's initialization, we should fix it initialization.

LGTM

I'm preparing a CL to fix the initialization

[michaeln, 2011-05-19 21:29:26]

> I'm preparing a CL to fix the initialization

Please take a look at the additions to webkit_thread.cc