[Webkit-unassigned] [Bug 65323] REGRESSION: r91931 causes NOTREACHED to be hit via StorageTracker

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu Jul 28 11:18:30 PDT 2011


https://bugs.webkit.org/show_bug.cgi?id=65323





--- Comment #3 from Brady Eidson <beidson at apple.com>  2011-07-28 11:18:31 PST ---
(In reply to comment #2)
> Oh dear...
> 
> It's not at all clear to me from this backtrace exactly what's going on - why 91931 caused this.  I was under the impression that Chromium didn't make use of the StorageTracker (I remember when we were adding it there was a lot of hubbub about making sure it doesn't affect Chromium because they didn't want it)
> 
> 91931 simple deferred StorageTracker initialization until the first time a storage area is accessed by the DOM.  That code path is common and always has to happen on the main thread.
> 
> From the background storage thread perspective, it is bizarre that there's any visible behavior change.

Oh duh, I think I realized what's going on.  By moving the initialization from WebKit to WebCore without platform guards, now *everyone* is getting an active, initialized StorageTracker.

That was a pretty bad mistake on my part.  My apologies - I'm working on a fix now.

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