[Webkit-unassigned] [Bug 98078] IndexedDB: IDBRequest/IDBCursor reference cycle not broken until transaction completes

[bugzilla-daemon at webkit.org]

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





--- Comment #1 from Joshua Bell <jsbell at chromium.org>  2012-10-03 10:47:35 PST ---
Created an attachment (id=166919)
 --> (https://bugs.webkit.org/attachment.cgi?id=166919&action=review)
Repro case for cursor issue

Attachd repro case c/o dbk at google.com from crbug.com/145982
A reproduction case is attached.  findversion_nestedincomplete produces the problem, and findversion_testfix is the same code patched to always exhaust the cursors.  _tab.html is the code running in a tab, _sw.html is the same running in a shared worker.  Run the _tab.html version first to allow the database to be established and populated.  Runs after that reuse the database and should be good for profiling purposes.

I could be wrong, but it didn't seem to me that the issue resolves itself after the transaction completes.  I was seeing persistently high memory use ongoing.  If I made NUM_DOCUMENTS and/or VALUE_SIZE large enough in these repro cases I could also cause reliable crashes while preforming the read transaction.  I would have thought memory use by a scan would be related to the max size of an object in the store, rather than its total size.

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