[Webkit-unassigned] [Bug 282093] New: IndexedDB breaks randomly | UnknownError: Error looking up record in object store by key range

[bugzilla-daemon at webkit.org]

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

            Bug ID: 282093
           Summary: IndexedDB breaks randomly | UnknownError: Error
                    looking up record in object store by key range
           Product: WebKit
           Version: Safari 17
          Hardware: Mac (Apple Silicon)
                OS: macOS 14
            Status: NEW
          Severity: Major
          Priority: P2
         Component: Website Storage
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: mark.langer at autoixpert.de
                CC: sihui_liu at apple.com

Created attachment 473040

  --> https://bugs.webkit.org/attachment.cgi?id=473040&action=review

Diagnostics Report MacOS - MacBook Apple Silicon

Every week, our users
* get errors writing or reading from IndexedDB.
* binary files inside IndexedDB are mixed up (the key with which an image file is stored returns a different image when reading it.)

This happens only on Apple devices and only with Safari. Hence, we can rule out own code errors.

Seen on:
* MacBook Pro (Apple Silicon)
* iPhones (iOS 17.4 and 18.0.1 - non-exhaustive list)
* iPads (iPadOS 17.4 and 18.0.1 - non-exhaustive list)

Error Messages include:
* UnknownError: Error looking up record in object store by key range
* AbortError
* Cannot open cursor to perform index gets in database (may be emitted by idb by Jake Archibald)

Short term solution:
* Quit Safari. Closing the window or opening a new tab doesn't help. Assumption: Some background service(s) is/are breaking.

Today, we saw a diagnostics report on a MacBook on com.apple.WebKit.WebContent happening while the error was reproducible.
Content: CPU above 50% for over 90 seconds.

Thought: There might be a threshold on Macs killing processes if they use too much CPU for too long?

Attachments:
* Diagnostics Report
* Console Logs Safari

-- 
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/20241025/13a200d7/attachment.htm>