WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
NEW
282093
IndexedDB breaks randomly | UnknownError: Error looking up record in object store by key range
https://bugs.webkit.org/show_bug.cgi?id=282093
Summary
IndexedDB breaks randomly | UnknownError: Error looking up record in object s...
Mark Langer
Reported
2024-10-25 06:38:38 PDT
Created
attachment 473040
[details]
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
Attachments
Diagnostics Report MacOS - MacBook Apple Silicon
(205.29 KB, text/plain)
2024-10-25 06:38 PDT
,
Mark Langer
no flags
Details
Console Logs Safari - MacBook Pro Apple Silicon
(19.25 KB, text/plain)
2024-10-25 06:39 PDT
,
Mark Langer
no flags
Details
WebKit Networking Diagnostic Log
(78.20 KB, text/plain)
2024-10-28 05:50 PDT
,
Mark Langer
no flags
Details
WebKit WebContent Diagnostic Log
(13.90 KB, text/plain)
2024-10-28 05:51 PDT
,
Mark Langer
no flags
Details
WebKit WebContent Diagnostic Log
(24.02 KB, text/plain)
2024-10-30 05:58 PDT
,
Mark Langer
no flags
Details
View All
Add attachment
proposed patch, testcase, etc.
Mark Langer
Comment 1
2024-10-25 06:39:30 PDT
Created
attachment 473041
[details]
Console Logs Safari - MacBook Pro Apple Silicon Attachment 2:
Mark Langer
Comment 2
2024-10-25 06:42:09 PDT
Possibly related, yet not resolved:
https://bugs.webkit.org/show_bug.cgi?id=277615
https://bugs.webkit.org/show_bug.cgi?id=273827
https://bugs.webkit.org/show_bug.cgi?id=197050
Mark Langer
Comment 3
2024-10-28 05:50:14 PDT
Today we had another incident with mixed up photo files from IndexedDB. The diagnostics reports showed two dubious events: 1) ----------- com.apple.WebKit.Networking Event: disk writes Action taken: none Writes: 2147.50 MB of file backed memory dirtied over 33710 seconds (63.71 KB per second average), exceeding limit of 24.86 KB per second over 86400 seconds Writes limit: 2147.48 MB Limit duration: 86400s Writes caused: 2147.50 MB 2) ----------- com.apple.WebKit.WebContent Event: cpu usage Action taken: none CPU: 90 seconds cpu time over 145 seconds (62% cpu average), exceeding limit of 50% cpu over 180 seconds CPU limit: 90s Limit duration: 180s CPU used: 90s CPU duration: 145s -------------- Quitting Safari and restarting it usually resolves the issue for a while.
Mark Langer
Comment 4
2024-10-28 05:50:49 PDT
Created
attachment 473062
[details]
WebKit Networking Diagnostic Log
Mark Langer
Comment 5
2024-10-28 05:51:12 PDT
Created
attachment 473063
[details]
WebKit WebContent Diagnostic Log
Mark Langer
Comment 6
2024-10-30 05:58:02 PDT
Created
attachment 473079
[details]
WebKit WebContent Diagnostic Log Today, we whitnessed the shuffling again with another customer on MacOS 15.0.1. WebContent caused a diagnostic log again.
Radar WebKit Bug Importer
Comment 7
2024-11-01 06:39:14 PDT
<
rdar://problem/139068307
>
Mark Langer
Comment 8
2025-03-04 01:14:23 PST
Hi Apple team! Are there any updates on this? The issue is still happening in the same ways as described above. The issue is still unassigned. Is there a brave engineer wanting to tackle this? 🦸🏼♂️🦸🏽♀️
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug