[Webkit-unassigned] [Bug 36671] window.openDatabase() always fails for new databases when using WebKit nightly with Safari 4.0.5

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Apr 2 14:17:06 PDT 2010


--- Comment #7 from Eric U. <ericu at chromium.org>  2010-04-02 14:17:05 PST ---
(In reply to comment #4)
> I still don't know *for sure* that this was 56293, but am still highly
> suspicious.
> What's happening is that in WebChromeClient::exceededDatabaseQuota(), Safari is
> asking for the current details for the database using
> DatabaseTracker::detailsForNameAndOrigin().
> Previously, Safari would actually get a valid answer from WebKit.
> Now, it's getting nothing back because the "too be created" database isn't
> found in m_proposedDatabases.

I haven't tried running a fix yet, but I'll bet this is the bug: the search
through m_proposed databases uses '==' to compare the SecurityOrigins, but it's
stored a threadsafeCopy, so a pointer comparison always fails.  It should be
using SecurityOriginHash to compare them.  I'll go get set up to test a fix.

Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

More information about the webkit-unassigned mailing list