Closed Bug 1440336 Opened 6 years ago Closed 6 years ago

Based on about:memory, profiler backend uses lots of memory even if profiler addon isn't installed nor the devtools profiler used.

Categories

(Core :: Gecko Profiler, defect)

Product:
Core
Component:
Gecko Profiler
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: smaug, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [MemShrink:P1]) 

In a process which has loaded just one tab containing a super simple web page, I see
├─────852,008 B (03.99%) -- profiler
│     ├──852,008 B (03.99%) ── profiler-state
│     └────────0 B (00.00%) ── lul
Whiteboard: [MemShrink]
Markus, can you take a look at this?
Flags: needinfo?(mstange)
Whiteboard: [MemShrink] → [MemShrink:P1]
The work in bug 1436179 should take care of most of this. Once that has landed, we should investigate if there's any low hanging fruit left.
Depends on: 1436179
Flags: needinfo?(mstange)
After bug 1436179 I don't see any profiler/profiler-state line without installing/starting the profiler, so I'm calling this fixed.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.