Closed Bug 1330730 Opened 5 years ago Closed 5 years ago
_about _pages .py Test About Pages .test _back _forward | application crashed [@ mozilla::a11y::Proxy Text Change Event(mozilla::a11y::Proxy Accessible *,ns String const &,int,unsigned int,bool,bool)]
Filed by: rvandermeulen [at] mozilla.com https://treeherder.mozilla.org/logviewer.html#?job_id=68394619&repo=mozilla-inbound https://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-inbound-win32-debug/1484223436/mozilla-inbound_win7_vm-debug_test-marionette-e10s-bm139-tests1-windows-build1075.txt.gz
Trevor, David, do you know what could have caused this ?
What caused it was inches away from where it was filed. https://treeherder.mozilla.org/#/jobs?repo=mozilla-inbound&fromchange=311a9929ce5baae9f383eacc8109b60f6f472987&group_state=expanded&filter-searchStr=61261767bf8478cbb7289b983152ce49b6884385&tochange=8cdcf83fd1659c563ad6569e5bd63ac99a73ba65
After bug 1329814 a DocAccessibleParent can be shutdown by the parent process before a content process has started shutting down the document that DocAccessibleParent represents. That means the content processcan send an event from a live document to a DocAccessibleParent that has already been destroyed.
Attachment #8826702 - Flags: review?(bugs)
This shouldn't be necessary because shutting down all the proxies and child documents should already do it, but we might as well be sure.
Attachment #8826709 - Flags: review?(dbolter)
5 years ago
Attachment #8826709 - Flags: review?(dbolter) → review+
Pushed by email@example.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/362ba8c68a29 ignore events delivered to a destroyed DocAccessibleParent r=smaug https://hg.mozilla.org/integration/mozilla-inbound/rev/2b34eb5807f3 make sure mAccessibles and mChildDocs are cleared by DocAccessibleparent::Destroy() r=davidb
5 years ago
You need to log in before you can comment on or make changes to this bug.