Closed Bug 1357481 Opened 7 years ago Closed 9 months ago

1.03ms uninterruptible reflow at appendPrompt@chrome://browser/content/browser.js:8426:5

Categories

(Firefox :: General, defect, P4)

Product:
Firefox
Component:
General
Type:
defect

Tracking

()

Status:
RESOLVED INCOMPLETE
Project Flags:
Performance Impact low

People

(Reporter: mconley, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: perf, Whiteboard: [ohnoreflow][fxperf:p3]) 

Here's the stack:

appendPrompt@chrome://browser/content/browser.js:8426:5
openTabPrompt@jar:file:///Applications/FirefoxNightly.app/Contents/Resources/omni.ja!/components/nsPrompter.js:412:21
openPrompt@jar:file:///Applications/FirefoxNightly.app/Contents/Resources/omni.ja!/components/nsPrompter.js:535:17
confirm@jar:file:///Applications/FirefoxNightly.app/Contents/Resources/omni.ja!/components/nsPrompter.js:634:9
reset@moz-extension://f406413e-5fc2-ff4d-94c7-889452f980de/content/report.js:109:9
handleEvent@moz-extension://f406413e-5fc2-ff4d-94c7-889452f980de/content/report.js:154:9
Flags: qe-verify?
Priority: -- → P2
Whiteboard: [ohnoreflow][qf][photon-performance] → [ohnoreflow][qf:p1][photon-performance]
Please correct if this isn't the right component. Thanks!
Component: Untriaged → General
Another stack:

appendPrompt@chrome://browser/content/browser.js:8469:5
openTabPrompt@resource:///modules/RemotePrompt.jsm:81:19
receiveMessage@resource:///modules/RemotePrompt.jsm:31:11
permitUnload@chrome://global/content/bindings/remote-browser.xml:357:13
_beginRemoveTab@chrome://browser/content/tabbrowser.xml:2684:46
removeTab@chrome://browser/content/tabbrowser.xml:2611:18
onxblclick@chrome://browser/content/tabbrowser.xml:6567:11
Another stack:

appendPrompt@chrome://browser/content/browser.js:8554:5
openTabPrompt@resource://gre/components/nsPrompter.js:412:21
openPrompt@resource://gre/components/nsPrompter.js:535:17
confirm@resource://gre/components/nsPrompter.js:634:9
reset@moz-extension://2ef81082-98ca-4f6e-91f4-964d699287b2/content/report.js:188:9
handleEvent@moz-extension://2ef81082-98ca-4f6e-91f4-964d699287b2/content/report.js:235:9
EventListener.handleEvent*init@moz-extension://2ef81082-98ca-4f6e-91f4-964d699287b2/content/report.js:41:5
@moz-extension://2ef81082-98ca-4f6e-91f4-964d699287b2/content/report.js:260:3
EventListener.handleEvent*@moz-extension://2ef81082-98ca-4f6e-91f4-964d699287b2/content/report.js:259:1
Priority: P2 → P3
Whiteboard: [ohnoreflow][qf:p1][photon-performance] → [ohnoreflow][qf:p1][reserve-photon-performance]
Flags: qe-verify? → qe-verify-
Whiteboard: [ohnoreflow][qf:p1][reserve-photon-performance] → [ohnoreflow][qf:p2][reserve-photon-performance]
Priority: P3 → P4
Keywords: perf
Whiteboard: [ohnoreflow][qf:p2][reserve-photon-performance] → [ohnoreflow][qf:p3][reserve-photon-performance]
Whiteboard: [ohnoreflow][qf:p3][reserve-photon-performance] → [ohnoreflow][qf:p3][fxperf]
Whiteboard: [ohnoreflow][qf:p3][fxperf] → [ohnoreflow][qf:p3][fxperf:p3]
Performance Impact: --- → P3
Whiteboard: [ohnoreflow][qf:p3][fxperf:p3] → [ohnoreflow][fxperf:p3]
Severity: normal → S3

Nothing in this bug points to the specific call that triggered the sync reflow, so it's difficult to say for sure if the code still exists. I tried to reproduce locally by calling alert() or confirm() in the devtools console. In profiles I saw multiple sync reflows, but none of them had a stack similar to the one reported here.

Status: NEW → RESOLVED
Closed: 9 months ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.