Here's the stack: BrowserOpenAddonsMgr/<@chrome://browser/content/browser.js:6577:7 Promise@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:390:5 BrowserOpenAddonsMgr@chrome://browser/content/browser.js:6551:10 oncommand@chrome://browser/content/browser.xul:1:1
This stack seems incomplete. I guess the promise in BrowserOpenAddonsMgr is what prevents getting a correct stack. The sync reflow is likely due to the openUILinkIn call (that moves the focus) at http://searchfox.org/mozilla-central/rev/7aa21f3b531ddee90a353215bd86e97d6974e25b/browser/base/content/browser.js#6587 or to the explicit .focus() call 8 lines later.
(In reply to Florian Quèze [:florian] [:flo] from comment #1) > the openUILinkIn call (that moves the focus) That's bug 1356858.
Whiteboard: [ohnoreflow][qf][photon-performance] → [ohnoreflow][qf:p3][photon-performance]
Priority: P2 → P3
Whiteboard: [ohnoreflow][qf:p3][photon-performance] → [ohnoreflow][qf:p3][reserve-photon-performance]
Whiteboard: [ohnoreflow][qf:p3][reserve-photon-performance] → [ohnoreflow][qf:p3][fxperf]
I can't reproduce this locally - I think this might have been fixed in the meantime.
Status: NEW → RESOLVED
Last Resolved: 2 months ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.