Julien Wajsberg [:julienw] Reporter
	Description • 7 years ago

After running Firefox for a long time (for example leaving it overnight), I always see it's lagging and I have to restart it.

Here are some logs while I'm in different websites:

Twitter (typing in a DM): https://perfht.ml/2mHlGQG
Perf HTML itself (merely moving the mouse over the timeline): https://perfht.ml/2mHmuW3
Bugzilla (entering this bug information in the textarea): https://perfht.ml/2mHmoxk

I use Aurora (v53 20170301084303 currently -- but it's happening to me for a very long time) with e10s and 1 process.

Some other info:

RSS measurements:
Web Content: 1.7GB
Firefox: 1.4GB

I attached my memory measurements.

Addons I use: uBlock Origin, REST Client

	Ben Kelly [:bkelly, not reviewing]
	Comment 1 • 7 years ago

Did you minimize memory before taking this measurement?  If so, it seems you are leaking devtools in the parent process:

│    │  ├────2.39 MB (00.15%) -- top(none)/detached
│    │  │    ├──1.78 MB (00.11%) ++ window(chrome://devtools/content/inspector/markup/markup.xhtml)
│    │  │    ├──0.60 MB (00.04%) ++ window(chrome://devtools/content/responsive.html/index.xhtml)
│    │  │    └──0.01 MB (00.00%) ── window([system])/dom/other [6]

And you have hundreds of about:blank windows in the parent process.

Next time this happens you could do this:

1) Open an example.com in a tab to hold the child process alive
2) Close all other tabs
3) Capture GC/CC verbose logs

These will be huge and can't be put in the bug.  We can analyze them using heapgraph tool to maybe find out what is causing the leak.

	Julien Wajsberg [:julienw] Reporter
	Comment 2 • 7 years ago

> Did you minimize memory before taking this measurement? 

No I didn't. Should I ?

> If so, it seems you are leaking devtools in the parent process

The devtools may have been opened in some tab -- not sure though.


> 2) Close all other tabs

That's my main profile, I don't really want to close all of them :)

That said I could keep a copy of the profile open for a long time and see if I can reproduce the issue.

	Eric Rahm [:erahm]
	Comment 3 • 7 years ago

This looks like more of a perf issue, clearing memshrink for now.

	Ciprian Muresan [:cmuresan], Ecosystem QA
	Comment 4 • 7 years ago

Julien, have you had some time to dig deeper into this issue?

	Julien Wajsberg [:julienw] Reporter
	Comment 5 • 7 years ago

Hey, no sorry.

I didn't seem to get the issue lately but I think I restarted Firefox more often to upgrade it.

	Ciprian Muresan [:cmuresan], Ecosystem QA
	Comment 6 • 7 years ago

Let's consider the issue Resolved-Worksforme for the time being, based on the last comment. 
Please reopen if you encounter it again in the future.

	Firefox Bug Husbandry Bot
	Comment 7 • 7 years ago

Moving from Core::Untriaged to Core::General https://bugzilla.mozilla.org/show_bug.cgi?id=1407598