Closed Bug 1099451 Opened 10 years ago Closed 10 years ago

tests that load about:home cause occasional NotFoundErrors from its indexedDB use

Categories

(Firefox :: General, defect)

defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: Gavin, Unassigned)

References

Details

Various Firefox search tests load about:home to test its search bar behavior. Those tests seem to all intermittently run into: 01:05:07 INFO - 1496 INFO TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/components/search/test/browser_bing_behavior.js | uncaught exception - NotFoundError: The operation failed because the requested database object could not be found. For example, an object store did not exist but was being opened. at chrome://browser/content/abouthome/aboutHome.js:256 This seems like an indexedDB bug of some sort at the core, possibly caused by tearing down the page while some indexedDB transaction is outstanding. These tests were split out into their own test (browser_abouthome_behavior.js) and disabled for e10s by http://hg.mozilla.org/mozilla-central/rev/4e83df89ebb8. These Firefox OS bugs may be related too: bug 1089543 bug 941680
I thought that error was not anymore reproducible in browser_abouthome_behavior.js. the existing tests were wrong cause they didn't wait a tick when detecting the mutation, so they were actually running before about:home had a chance to setup indexedDB. The test has been disabled on e10s due to leaks, we had leaks in the past cause indexedDB keeps the global window alive longer than usual to complete operations. In the past this was fixed by making gc+cc run twice before reporting leaks. Not sure what is causing the current leaks (if that code somehow broke or it's not enough anymore).
Indeed looks like this is no longer an issue...
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.