Closed
Bug 1410482
Opened 8 years ago
Closed 7 years ago
enable AOM for privileged content
Categories
(Core :: DOM: Core & HTML, enhancement, P2)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
FIXED
mozilla62
Tracking | Status | |
---|---|---|
firefox62 | --- | fixed |
People
(Reporter: surkov, Assigned: surkov)
References
Details
Attachments
(1 file, 2 obsolete files)
3.29 KB,
patch
|
smaug
:
review+
|
Details | Diff | Splinter Review |
No description provided.
Assignee | ||
Comment 1•8 years ago
|
||
Olli, who's a good candidate to review? You're not accepting those.
Flags: needinfo?(bugs)
Assignee | ||
Comment 2•8 years ago
|
||
Comment 3•8 years ago
|
||
I could review next week, if that is ok.
Could you use AddBoolVarCache and not GetBool. The cache is quite a bit faster.
Flags: needinfo?(bugs)
Assignee | ||
Comment 5•8 years ago
|
||
(In reply to Olli Pettay [:smaug] (work week Oct 16-20) from comment #3)
> I could review next week, if that is ok.
sure, thank you.
> Could you use AddBoolVarCache and not GetBool. The cache is quite a bit
> faster.
I will, np, I didn't know it may be a hot path. I guess it's invoked not only once when the browser starts up?
Assignee | ||
Comment 6•8 years ago
|
||
address Olli's comments
Attachment #8920653 -
Attachment is obsolete: true
Attachment #8921044 -
Flags: feedback?(bugs)
Assignee | ||
Comment 7•8 years ago
|
||
apparently attached a wrong patch, fixed
Attachment #8921044 -
Attachment is obsolete: true
Attachment #8921044 -
Flags: feedback?(bugs)
Attachment #8921045 -
Flags: feedback?(bugs)
Comment 8•8 years ago
|
||
Comment on attachment 8921045 [details] [diff] [review]
aomenable
[Func="mozilla::dom::AccessibleNode::IsAOMEnabled"] isn't probably needed.
I'd expect [Func="AccessibleNode::IsAOMEnabled"] to work too, assuming AccessibleNode uses namespaces and such in the normal way.
Attachment #8921045 -
Flags: feedback?(bugs) → review+
Assignee | ||
Comment 9•8 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/2602e10160a18c0b998c749d8aa2005fc8ef6614
Bug 1410482 - enable AOM for privileged content, r=smaug
![]() |
||
Comment 10•8 years ago
|
||
Backed out for leaks in devtools tests:
https://hg.mozilla.org/integration/mozilla-inbound/rev/9fddd9d18e1d1d879598b1a1e42e15cc17783cee
Push with failures: https://treeherder.mozilla.org/#/jobs?repo=mozilla-inbound&revision=2602e10160a18c0b998c749d8aa2005fc8ef6614&filter-resultStatus=usercancel&filter-resultStatus=runnable&filter-resultStatus=testfailed&filter-resultStatus=busted&filter-resultStatus=exception&filter-resultStatus=retry
Different push which also ran asan failure: https://treeherder.mozilla.org/#/jobs?repo=mozilla-inbound&revision=d84ea38d6fd086a627f0321be28103be88fad175&filter-resultStatus=usercancel&filter-resultStatus=runnable&filter-resultStatus=testfailed&filter-resultStatus=busted&filter-resultStatus=exception&filter-resultStatus=retry
Failure log debug: https://treeherder.mozilla.org/logviewer.html#?job_id=138962123&repo=mozilla-inbound
> TEST-UNEXPECTED-FAIL | leakcheck | tab process: 407504 bytes leaked (APZEventState, ActiveElementManager, AsyncLatencyLogger, BackstagePass, CSPService, ...)
Failure log asan: https://treeherder.mozilla.org/logviewer.html#?job_id=138978815&repo=mozilla-inbound
Flags: needinfo?(surkov.alexander)
Updated•7 years ago
|
Priority: -- → P2
Assignee | ||
Comment 11•7 years ago
|
||
Assignee | ||
Comment 12•7 years ago
|
||
Assignee | ||
Comment 13•7 years ago
|
||
Assignee | ||
Comment 14•7 years ago
|
||
Assignee | ||
Comment 15•7 years ago
|
||
Assignee | ||
Comment 16•7 years ago
|
||
Assignee | ||
Comment 17•7 years ago
|
||
Assignee | ||
Comment 18•7 years ago
|
||
Assignee | ||
Comment 19•7 years ago
|
||
Assignee | ||
Comment 20•7 years ago
|
||
Assignee | ||
Comment 21•7 years ago
|
||
Assignee | ||
Comment 22•7 years ago
|
||
Assignee | ||
Comment 23•7 years ago
|
||
Assignee | ||
Comment 24•7 years ago
|
||
Assignee | ||
Comment 25•7 years ago
|
||
Assignee | ||
Comment 26•7 years ago
|
||
Assignee | ||
Comment 27•7 years ago
|
||
Assignee | ||
Comment 28•7 years ago
|
||
Assignee | ||
Comment 29•7 years ago
|
||
Assignee | ||
Comment 30•7 years ago
|
||
AccessibilityService is connected/caused with the leaks. If no GetOrCreateService() is called by AOM object, then no leaks.
Good build:
https://hg.mozilla.org/try/rev/1c81188d5618066332ba623fd3c26ebbc859790d
https://treeherder.mozilla.org/#/jobs?repo=try&revision=1c2e746ebbe929bfbdd836e8a7a9f3b97ecd39a4
Bad build:
https://hg.mozilla.org/try/rev/34317d2fdf9c9954aca9af303fb33d0e653ec457
https://treeherder.mozilla.org/#/jobs?repo=try&revision=1f2347d35a57c2af114f1f4382cdc997b874dfdf&selectedJob=158252012
[1] points out to nsComponentManagerImpl. The interesting thing is the logs has a line of:
Marionette DEBUG Received observer notification "xpcom-shutdown"
after leak reports. Since we use "xpcom-shutdown" to shutdown accessibility service, then it makes me wonder if this could be a timing issue.
Olli, do you have any suggestions/advices how to investigate the issue further?
[1] https://treeherder.mozilla.org/logviewer.html#?job_id=158252265&repo=try&lineNumber=166708
Flags: needinfo?(surkov.alexander) → needinfo?(bugs)
Comment 31•7 years ago
|
||
Does someone perhaps create the service after xpcom-shutdown?
Flags: needinfo?(bugs)
Assignee | ||
Comment 32•7 years ago
|
||
Assignee | ||
Comment 33•7 years ago
|
||
(In reply to Olli Pettay [:smaug] from comment #31)
> Does someone perhaps create the service after xpcom-shutdown?
unlikely, I tried to crash the browser [1] if somebody makes attempt to initialize AccessibilityService after XPCOM shutdown. No crash [2].
[1] https://treeherder.mozilla.org/#/jobs?repo=try&revision=a9d29ff0f57ce5ae1959ecdc4fbd440179a39b8b&selectedJob=158534669
[2] https://hg.mozilla.org/try/rev/ac7671a7d94f0f34100cd598cc5f1a0ed360693e
Assignee | ||
Comment 34•7 years ago
|
||
Assignee | ||
Comment 35•7 years ago
|
||
Olli, any other advice how to approach it, or maybe names of who was working in this area and might have ideas?
Flags: needinfo?(bugs)
Comment 36•7 years ago
|
||
hmm, so do we leak AccessibleNodes? What is the most recent link a leak log?
I'm trying to recall the ownership model of AccessibleNodes. Why we aren't cycle collecting its member variables?
Flags: needinfo?(bugs)
Assignee | ||
Comment 37•7 years ago
|
||
Assignee | ||
Comment 38•7 years ago
|
||
Assignee | ||
Comment 39•7 years ago
|
||
seems passing now, not sure what was a fix, will land it
Comment 40•7 years ago
|
||
Pushed by surkov.alexander@gmail.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/8589b95008dd
enable AOM for privileged content, r=smaug
Comment 41•7 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 7 years ago
status-firefox62:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla62
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•