Open Bug 1433399 Opened 7 years ago Updated 2 years ago

memory snapshot includes objects that gc can free

Categories

(Toolkit :: about:memory, defect)

Product:
Toolkit
Component:
about:memory
Version:
57 Branch
Type:
defect

Tracking

()

Status:
UNCONFIRMED

People

(Reporter: ossman, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:57.0) Gecko/20100101 Firefox/57.0 Build ID: 20171130114058 Steps to reproduce: Run noVNC playback test multiple times in order too see if there are any memory leaks. Actual results: Firefox memory profiler shows large amount (123 MiB) of memory still allocated. Opening about:memory and running the GC frees up the vast majority of memory (116 MiB). Expected results: The memory profiler should not include, or at least clearly separate, the memory that will be freed up the next time the GC is run. Otherwise it is impossible to tell how much memory is actually needed (or lost).
Component: Untriaged → about:memory
Product: Firefox → Toolkit
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.