Closed
Bug 1752622
Opened 3 years ago
Closed 2 years ago
Profile memory use when switching tabs
Categories
(GeckoView :: General, task, P1)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: owlish, Assigned: kaya)
References
(Blocks 1 open bug)
Details
(Whiteboard: [geckoview:2022h2] [geckoview:m108] [geckoview:m109])
To solve the problem of the tab reloading, we need to understand what kind of metrics and telemetry related to tabs, tab use and memory footprint we already have.
- There is data on the amount of tabs open simultaneously. We need to access and examine that data (chutten would be the person to ask about our telemetry documentation)
If the investigation reveals we need more data, feel free to file new bugs for that.
Updated•3 years ago
|
Severity: -- → S3
Priority: -- → P2
Updated•2 years ago
|
Whiteboard: [geckoview:2022h2?]
Comment 1•2 years ago
|
||
108
Assignee: nobody → kkaya
status-firefox105:
--- → wontfix
status-firefox106:
--- → wontfix
status-firefox107:
--- → wontfix
Priority: P2 → P1
Summary: Investigate metrics on memory use → Profile memory use when switching tabs
Whiteboard: [geckoview:2022h2?] → [geckoview:2022h2] [geckoview:m108]
Comment 2•2 years ago
|
||
Kaya will continue to investigate memory in 109.
status-firefox105:
wontfix → ---
status-firefox106:
wontfix → ---
status-firefox107:
wontfix → ---
Whiteboard: [geckoview:2022h2] [geckoview:m108] → [geckoview:2022h2] [geckoview:m108] [geckoview:m109]
Assignee | ||
Comment 3•2 years ago
|
||
There is no significant memory issues happening while switching the tabs. There is no memory leak while switching the tabs. No unnecessary allocations in the heap. The Android Studio profiler shows a steady line for the memory usage while switching between the tabs. I think we can close this issue.
Assignee | ||
Updated•2 years ago
|
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•