Bug 193504 - Memory leak with IDB openCursor()
Summary: Memory leak with IDB openCursor()
Status: RESOLVED CONFIGURATION CHANGED
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebCore JavaScript (show other bugs)
Version: Safari 12
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-01-16 12:21 PST by zac spitzer
Modified: 2022-07-01 18:49 PDT (History)
4 users (show)

See Also:


Attachments
leak demonstration (1.79 KB, text/html)
2019-01-16 12:21 PST, zac spitzer
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description zac spitzer 2019-01-16 12:21:49 PST
Created attachment 359291 [details]
leak demonstration

Safari seems to leaks memory with indexedDB and openCursor(), Chrome is fine, Firefox also has problems

Run the attached test case with the web inspector open, 85 MB will be leaked from one record
Comment 1 zac spitzer 2019-01-17 03:31:16 PST
This is still a problem in Tech Preview 73
Comment 2 zac spitzer 2019-01-29 12:40:47 PST
This was previously discovered and reported via the Apple bug reporter

https://qiita.com/smith/items/16d48083fe7a7e4b70ee
Comment 3 Sihui Liu 2022-07-01 18:49:06 PDT
I am not able to reproduce the memory increase when reloading test page in Safari; I think the leak might be fixed by some previous changes like https://bugs.webkit.org/show_bug.cgi?id=193167.

If you still see memory increase, please provide a new test case and we will look into it again.