Closed Bug 1815579 Opened 2 years ago Closed 2 years ago

Investigate janky Tabs Tray in Compose performance

Categories

(Fenix :: Performance, defect)

All
Android
defect

Tracking

(Performance Impact:low, firefox116 fixed)

RESOLVED FIXED
116 Branch
Performance Impact low
Tracking Status
firefox116 --- fixed

People

(Reporter: matt-tighe, Assigned: 007)

References

Details

(Whiteboard: [fxdroid])

Attachments

(1 file)

The Tabs Tray conversion in Compose runs noticeably slower than the XML version when many tabs (30+) are open. This was discovered during this investigation.

STR:

  1. Open 30+ tabs in a debug build or build with the composeTabsTray otherwise enabled.
  2. Scroll up and down continuously.

This will demonstrate the slowness and may even result in a crash with no Logcat entry or system dialog. This crash seems to be caused by hitting a hard memory limit.

Using the profiler @007 and I saw instances where the memory usage would continue to balloon as scrolling happened, until it became 4 or 5 times larger than idle. It would eventually drop down to nominal levels after some inactivity, but this seemed to take ~30 seconds. This memory ballooning seemed to be related to either Bitmap usage or Autosave::triggerSave.

These performance issues should be investigated and resolved before the feature can be released.

See Also: → 1815306

Note that https://bugzilla.mozilla.org/show_bug.cgi?id=1815306#c7 includes a small script for launching a large number of tabs that may be helpful during investigation.

Blocks: 1814998
See Also: → 1815620

This is likely due to how the Favicons are being loaded. The initial investigation here should be around the ThumbnailCard Composable which TabListItem and TabGriditem ultimately use.

Depends on: 1814994
Assignee: nobody → nbond
Status: NEW → ASSIGNED

The Performance Impact Calculator has determined this bug's performance impact to be low. If you'd like to request re-triage, you can reset the Performance Impact flag to "?" or needinfo the triage sheriff.

Platforms: Android
Impact on browser: Causes noticeable jank

Performance Impact: --- → low
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
Flags: qe-verify+
Resolution: --- → FIXED
Target Milestone: --- → 116 Branch
Flags: qe-verify+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: