[Webkit-unassigned] [Bug 178204] IndexedDB causes massive storage usage on iOS, never recycles usage

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Sat Jun 23 10:21:14 PDT 2018


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

Mohammad Shraim <moh.shraim at hotmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |moh.shraim at hotmail.com

--- Comment #3 from Mohammad Shraim <moh.shraim at hotmail.com> ---
Face the same problem on iOS 11.2 and 11.4
Sent apple bug reporter details 2 days ago..

The problem exist on Safari, Chrome and Any application using WKWebView with IndexDB.

to Reproduce the problem on any iOS device i made simple page https://ssbyte.com/dbtest/

To see the big increase in Application Data on any iOS device just open the link on Safari Or Chrome.
* keep repeat the steps of open Safari Or Chrome And closing the application..

Generally every time you will see increase from 0.1 to 2.5 MB in the application data..

I Traced the problem on WKWebView Sample application and Found the FOLOWWING:

To detect the increment we download the device application container through xCode; at application container we found the source of increment on the following file; IndexedDB.sqlite3-wal
and this was the location of file at container:
AppData/Library/WebKit/WebsiteData/IndexedDB/file__0/dbName/IndexedDB.sqlite3-wal

according to https://www.sqlite.org/tempfiles.html

2.2. Write-Ahead Log (WAL) Files
A write-ahead log or WAL file is used in place of a rollback journal when SQLite is operating in WAL mode. As with the rollback journal, the purpose of the WAL file is to implement atomic commit and rollback. The WAL file is always located in the same directory as the database file and has the same name as the database file except with the 4 characters "-wal" appended. The WAL file is created when the first connection to the database is opened and is normally removed when the last connection to the database closes. However, if the last connection does not shutdown cleanly, the WAL file will remain in the filesystem and will be automatically cleaned up the next time the database is opened.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20180623/f8e47138/attachment.html>


More information about the webkit-unassigned mailing list