To clarify 

> Did this work before? Yes not sure

Did this work before?  Yes
What version? not sure

Correction, apologies, I confused myself with all the browser testing.

Works in Chrome on macOS
Doesn't work in Chrome on Windows

So its just on Windows it doesn't work.

Also works in Microsoft Edge on Windows.

austin.france@ - Thanks for filing the issue...!!

Could you please provide a sample test file/url to test the issue from TE-end.
This will help us in triaging the issue further.

Thanks...!!

If Platform>DevTools means inspector/debugger, then I must make it clear, it isn't specific to devtools, it is a problem in the browser, not in devtools.

The code to reproduce this can be found in the opening comment.  Attached that code as a file for your convenience.

No idea what TE-end means.

Deleted: indexeddb.html 138 bytes

indexeddb.html 138 bytes View Download

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Unable to reproduce the issue on Win-10 using chrome reported version #64.0.3282.167 and latest canary #66.0.3352.0.

Attached a screen cast for reference.

Following are the steps followed to reproduce the issue.
------------
1. Opened the attached file "indexeddb.html"
2. Observed that console showed a success event as expected.

austin.france@ - Could you please check the issue on latest canary #66.0.3352.0 by creating a new profile without any apps and extensions and please let us know if the issue still persist or not.

Thanks...!!

Deleted: 814292.mp4 546 KB

	814292.mp4 546 KB View Download

Chrome Canary doesn't work at all.  Everything just awe snaps.  chrome://about and trying to open indexeddb.html as well as new tab.  This being a brand new install of canary, using --user-data-dir to create a new profile.

Deleted: chrome-canary-dev-profile.png 45.3 KB

	chrome-canary-dev-profile.png 45.3 KB View Download

Deleted: chrome-canary-aw-snap.png 16.3 KB

	chrome-canary-aw-snap.png 16.3 KB View Download

Ran normal chrome, with --user-data-dir pointing at empty folder, and indexeddb.html works fine.  So something to do with my normal chrome profile I guess.

I can see the indexeddb folders from my tests in my profile.  

http_10.119.103.2_0_indexeddb.blob
http_10.119.103.2_0_indexeddb.leveldb

file__0_indexeddb.leveldb

and the contents of file__0_indexedbd.leveldb look identical to the contents in the profile thats working, just that in my normal profile (with or without --disable-extensions) the events don't fire.

Happy for this to be put down to a corrupt profile and remove it, though I will wait to see if you need any further info before I do.

Deleted: indexeddb-in-profile.png 32.6 KB

	indexeddb-in-profile.png 32.6 KB View Download

Deleted: chrome-no-extensions-broken.png 38.1 KB

	chrome-no-extensions-broken.png 38.1 KB View Download

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

As per comment #10 and #11, it seems that the issue is profile specific and also the issue is not reproducible from TE-end. Hence, removing the Needs-Bisect label and requesting someone from Blink>Storage>IndexedDB team to please have a look into the issue.

Thanks...!!

This should be fixed in m66 with https://chromiumdash.appspot.com/commit/2a9a8201b8c0b213aa41b6a390e9324113176f15

If you use m65 (which I believe is Beta right now), try launching chrome with this feature disabled: LevelDBFileHandleEviction

so --disabled-features=LevelDBFileHandleEviction

Whoops, --disable-features=LevelDBFileHandleEviction

IF this fixes the problem, please let me know! this will confirm the issue.

Duplicate bug here: https://bugs.chromium.org/p/chromium/issues/detail?id=795369

I'm going to keep this one open in case there is a confirmation of the problem.

It works on m65 anyway, with or without that option. So, to clarify, it's only an issue for me on m64 using my existing profile.

My issue doesn't sound like the same as 795369, unless you think its stuck opening the db and never times out, so I never get an event.

The DB being opened is a new db, rather than an existing one, so the browser just created it.  Can change the db name in the test html and observe the same behaviour.

This should be fixed.