[Webkit-unassigned] [Bug 82776] [DumpRenderTree] IndexedDB: Each page group/worker has a distinct IDBFactoryBackend
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Thu Feb 14 09:40:44 PST 2013
https://bugs.webkit.org/show_bug.cgi?id=82776
--- Comment #3 from Joshua Bell <jsbell at chromium.org> 2013-02-14 09:43:01 PST ---
(In reply to comment #2)
> (In reply to comment #1)
> > This does not affect the Chromium port, only DumpRenderTree.
>
> Why?
In full-blown Chromium, the back-end objects run in a different process; all front-end objects talk through proxies which implement IPC to the same back-end. This is true in Chromium's chrome browser and content_shell.
The Chromium port of test_shell (used for DumpRenderTree) is single-process, and runs into the issue in the bug Description.
> What about other ports?
Other ports did not implement IndexedDB at the time I wrote that. I don't know the state of the other ports at the moment, but they would likely run into this issue unless they implement a similar mechanism for separating front- and back-ends.
--
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