Closed Bug 1355861 Opened 8 years ago Closed 7 years ago

PageThumbsProtocol.js' newChannel2 implementation is slow

Categories

(Firefox :: New Tab Page, defect, P4)

defect

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: florian, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [fxperf])

See this profile: https://perfht.ml/2oyWRLz It was taken on an old netbook, it's part of the profile I got when opening a new tab (so loading about:newtab for the first time), https://perfht.ml/2oyXYuH
Flags: qe-verify?
Priority: -- → P2
Whiteboard: [photon-performance]
Priority: P2 → P3
Whiteboard: [photon-performance] → [reserve-photon-performance]
Flags: qe-verify? → qe-verify-
Priority: P3 → P4
Whiteboard: [reserve-photon-performance] → [fxperf]
PageThumbsProtocol was re-implemented in native code in bug 1373258, so I doubt that the profile from comment 0 is of much use anymore. florian, have you seen this appear in profiles lately, or can I close this out as incomplete?
Flags: needinfo?(florian)
(In reply to Mike Conley (:mconley) (:⚙️) (Totally backlogged on reviews and needinfos) from comment #1) > PageThumbsProtocol was re-implemented in native code in bug 1373258, so I > doubt that the profile from comment 0 is of much use anymore. florian, have > you seen this appear in profiles lately, or can I close this out as > incomplete? Let's close this.
Status: NEW → RESOLVED
Closed: 7 years ago
Flags: needinfo?(florian)
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.