Closed Bug 1651767 Opened 4 years ago Closed 4 years ago

Huge spike in memory and processor usage when opening a new tab

Categories

(Core :: Performance, defect)

80 Branch
defect

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: zorroguevara, Unassigned)

Details

Attachments

(2 files)

Attached file memory-report.json.gz

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:80.0) Gecko/20100101 Firefox/80.0

Steps to reproduce:

  1. Start Firefox
  2. Go browse some pages (open like 4 tabs)
  3. Wait around 2 min
  4. Open a new tab and go to a website (I tried Wikipedia)

Actual results:

  1. Memory used is higher than usual
  2. Huge spike in memory and processor

Expected results:

No spike of memory and processor

Attached file about - support.txt

I added the about:support copy/paste data in the .txt. Don't hesitate to ask me more data, I can also live-share also my screen if needed.
It's actually pretty bad and critical bug, I can't use Nightly a lot before my fan goes crazy.

I'll try to take a look at the memory report today.

Flags: needinfo?(continuation)

This from the main process looks a little high:
104.10 MB (19.56%) -- startup-cache

This also seems like a lot, but maybe it is normal:
├───35.29 MB (06.63%) -- images
│ ├──34.51 MB (06.48%) -- chrome
│ │ ├──34.34 MB (06.45%) -- vector/used/progress=18f
│ │ │ ├──27.66 MB (05.20%) -- image(0x0, chrome://browser/skin/tabbrowser/loading-burst.svg)

Generally, though, the memory usage doesn't look that high to me, from the memory report.

Maybe a profiler report would be more useful?

I've tried to make the summary a bit more specific.

Flags: needinfo?(continuation)
Summary: Firefox use a lot of memory → Huge spike in memory and processor usage when opening a new tab

Thank you for investigating it. I don't know if the memory is enough to investigate, given it happens a a few times: spike and then going down.
Last update make things better, I should see for the next days (till Friday) and tell if it's back to normal.

Component: Untriaged → Performance
Product: Firefox → Core

It looks good now. I'm closing it.

Status: UNCONFIRMED → RESOLVED
Closed: 4 years ago
Resolution: --- → INACTIVE

Thanks for the update. I'm glad your problem went away.

Resolution: INACTIVE → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: