indexedDB.open().onerror called with null event.target.error (race condition)

Fixed Issue #9978479

Details

Author
Nolan L.
Created
Nov 28, 2016
Privacy
This issue is public.
Found in
  • Microsoft Edge
  • Internet Explorer
Reports
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

There appears to be a race condition in IE/Edge IndexedDB that causes the open() request’s onerror method to be called with a null error. This can be reproduced by rapidly opening/destroying two databases with different names. Spacing them out with e.g. setTimeout(fn, 1000) fixes the problem.

This bug cannot be reproduced in Safari 10, Chrome, or Firefox. it’s Edge/IE only and can be reproduced in Edge 14975.100 and IE11 on the same Windows version.

Repro:

  1. Go to http://bl.ocks.org/nolanlawson/raw/9af8f79637b6f0d553ee121ef6fdd428/index.html?grep=test%5C.changes%5C.js-local
  2. Open F12 Console
  3. Notice all the “Failed to open indexedDB, are you in private browsing mode?”

Note that we do do some UA-sniffing for Edge/IE in the PouchDB, codebase, but this particular codepath is not UA-sniffing, so this is a true Edge bug.

Related PouchDB issue: https://github.com/pouchdb/pouchdb/issues/5949

Attachments

0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Ibrahim O.”

      Changed Assigned To to “Venkat K.”

      Changed Assigned To from “Venkat K.” to “Shawn P.”

      Changed Status to “Confirmed”

      Changed Status from “Confirmed” to “Not reproducible”

      Changed Status from “Not reproducible” to “Fixed”

    • Hello,

      Thank you for providing this information about the issue. We are pleased to report this feature is fixed in Edge 16299 and is available in our latest Creator’s Update build.

      Best Wishes,
      The MS Edge Team

    You need to sign in to your Microsoft account to add a comment.

    Sign in