javascript - What is the meaning of Chrome's IndexedDB error "Internal error checking key existence"? -


i'm getting error message intermittently within relatively large project @ seemingly arbitrary times (which makes me suspect race condition somewhere...), unfortunately don't have minimal example illustrating problem not understand root cause. basically, error signal event.target.webkiterrormessage "internal error checking key existence". don't understand error message supposed mean.

googling phrase returns 7 results (although more once google , others find question). these results either chromium source code or bug reports adding more detailed error messages chromium. not intimately familiar chromium's indexeddb backend implementation, 1 thing i'm struggling understand error message means in terms of frontend javascript code. instance, kinds of javascript mistakes can lead error message?

the code in question seems work fine in firefox, fwiw.

edits below

i also, more rarely, null returned cursor in response opencursor request key know real key. inconsistent - happens different keys , rarely. , it's in chrome. bizarre.

and i'm not sure if it's relevant, happens within large transaction many updates in 2 object stores (these ones leading null opencursor problems) , many adds in object store (this seems source of "internal error checking key existence" error). try make minimal example of , investigate further, regardless of how turns out, i'd still know answer original question, "internal error checking key existence" means.

another edit

after playing around more, ran weird transient error message, "internal error: backing store error performing put/add". i'd curious implies javascript.

also, validated of these problems new chrome 26 (and remain in chrome 27). downgrading chrome 25 makes these problems disappear... maybe bug in chrome...

one more edit

all of these problems seem happen in linux (i'm using ubuntu 12.10). in windows xp vm chrome 26, can't reproduce of these errors. submitted bug report it's becoming increasingly clear due bug, i'm not sure if i've narrowed down issue enough find solution.

as mentioned in edit question, submitted a bug report. has seemingly been resolved in chrome 28. experiencing problem in older versions of chrome, upgrade unstable version or wait couple months chrome 28 stable. , if gets errors in chrome 28 or higher, it's bug.


Comments

Popular posts from this blog

ios - iPhone/iPad different view orientations in different views , and apple approval process -

java Extracting Zip file -

C# WinForm - loading screen -