You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you have CueKeeper open in two windows, making a change will often cause one of them to fail with IndexedDB transaction (RO) failed: AbortError: (no message) (error code 0).
I've done some testing on @avsm's Mac mini (thanks!) and can now reproduce the error with a few lines of JavaScript:
Open a test database, creating a single key=value pair if it doesn't exist.
Attempt to read the value of the key ten times, once per second.
If you open this in two windows in Safari at once, one of them will likely fail with AbortError. I've reported it, but if they don't fix it quickly we might need to introduce some kind of random back-off-and-retry on abort.
The text was updated successfully, but these errors were encountered:
If you have CueKeeper open in two windows, making a change will often cause one of them to fail with
IndexedDB transaction (RO) failed: AbortError: (no message) (error code 0)
.I've done some testing on @avsm's Mac mini (thanks!) and can now reproduce the error with a few lines of JavaScript:
http://test.roscidus.com/static/idb_reads.html
The page will:
If you open this in two windows in Safari at once, one of them will likely fail with AbortError. I've reported it, but if they don't fix it quickly we might need to introduce some kind of random back-off-and-retry on abort.
The text was updated successfully, but these errors were encountered: