(In reply to James Teh [:Jamie] from comment #2) > Can you provide details as to why my patch in bug 1118086 seems to be the culprit? I don't see any a11y calls in the stack. That patch doesn't change any state that might cause an object to have a different lifecycle except when a particular attribute is set on a popup, but that attribute is currently never set. Of course, checking for that attribute still happens, but I'd expect to see the a11y call in the stack if that were the culprit. I think this was introduced with the landing of bug 1118086 because of [parsed log](https://treeherder.mozilla.org/#/jobs?repo=autoland&selectedJob=289183212&revision=8deec41015664a5fc52f4bf3d6a3c524e71585ac).
Bug 1615976 Comment 3 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to James Teh [:Jamie] from comment #2) > Can you provide details as to why my patch in bug 1118086 seems to be the culprit? I don't see any a11y calls in the stack. That patch doesn't change any state that might cause an object to have a different lifecycle except when a particular attribute is set on a popup, but that attribute is currently never set. Of course, checking for that attribute still happens, but I'd expect to see the a11y call in the stack if that were the culprit. I was thinking this was introduced with the landing of bug 1118086 because of [parsed log](https://treeherder.mozilla.org/#/jobs?repo=autoland&selectedJob=289183212&revision=8deec41015664a5fc52f4bf3d6a3c524e71585ac), so I needinfo you to do the examination.