Sammerb Reporter
	Description • 7 years ago

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0
Build ID: 20160905130425

Steps to reproduce:

We have an internal application which uses ajax requests to fetch updated information. The AJAX requests can be as fast as 200ms. 

I am using Firefox ESR 45.4

I have enclosed the memory report below.


Actual results:

This amkes firefox unresponsive and affects other tabs too!

Memory Report:
Main Process

WARNING: the following values are negative or unreasonably large.

    explicit/gfx
    explicit/gfx/heap-textures
    explicit/heap-unclassified 

This indicates a defect in one or more memory reporters. The invalid values are highlighted.
Explicit Allocations

1,254,266,387 B (100.0%) -- explicit
├──4,298,431,456 B (342.70%) -- gfx [?!]
│  ├──4,294,965,136 B (342.43%) ── heap-textures [?!]
│  ├──────2,668,448 B (00.21%) ── font-shaped-words
│  ├────────433,552 B (00.03%) ── font-cache
│  ├────────246,320 B (00.02%) ── font-list
│  ├────────115,120 B (00.01%) ── font-charmaps
│  └──────────2,880 B (00.00%) ── font-tables
├────418,308,216 B (33.35%) ++ window-objects
├────317,918,658 B (25.35%) ++ js-non-window
├─────64,405,086 B (05.13%) ++ heap-overhead
├─────16,491,876 B (01.31%) ++ add-ons
├─────15,708,048 B (01.25%) ++ storage
├──────9,788,436 B (00.78%) ++ xpconnect
├──────8,463,971 B (00.67%) ++ startup-cache
├──────8,257,778 B (00.66%) ++ network
├──────7,917,568 B (00.63%) ++ cycle-collector
├──────7,788,348 B (00.62%) ++ workers/workers(chrome)
├──────6,745,136 B (00.54%) ++ atom-tables
├──────4,678,120 B (00.37%) ++ images
├──────3,145,760 B (00.25%) ── dom/event-listener-managers-hash
├──────2,276,196 B (00.18%) ── icu
├──────2,122,142 B (00.17%) ── spell-check
├──────1,012,440 B (00.08%) ++ layout
├────────876,672 B (00.07%) ── xpti-working-set
├────────400,760 B (00.03%) ── preferences
├────────347,536 B (00.03%) ── telemetry
├────────329,288 B (00.03%) ++ xpcom
├────────100,016 B (00.01%) ── script-namespace-manager
├─────────65,328 B (00.01%) ── history-links-hashtable
├─────────42,592 B (00.00%) ── cookie-service
├──────────────0 B (00.00%) -- media
│              ├──0 B (00.00%) ── libnestegg
│              ├──0 B (00.00%) ── libogg
│              └──0 B (00.00%) ── libvpx
└──-3,941,355,040 B (-314.24%) ── heap-unclassified [?!]


Expected results:

Firefox should not become unresponsive and affect performance of other tabs.

	Loic
	Comment 1 • 7 years ago

Could you provide a self-contained testcase or an access (even limited on a testing server e.g.) to the app?

	Andrew McCreight [:mccr8]
	Comment 2 • 7 years ago

The heap-textures thing is probably a bug in the memory reporter.

You also need to attach the actual memory report to this bug, please. Knowing window objects are a few hundred MB doesn't tell us anything. You can use the anonmyzing option that will hide URLs.

	Sammerb Reporter
	Comment 3 • 7 years ago

(In reply to Loic from comment #1)
> Could you provide a self-contained testcase or an access (even limited on a
> testing server e.g.) to the app?

I am trying to set this up!

	Sammerb Reporter
	Comment 4 • 7 years ago

(In reply to Andrew McCreight [:mccr8] from comment #2)
> The heap-textures thing is probably a bug in the memory reporter.
> 
> You also need to attach the actual memory report to this bug, please.
> Knowing window objects are a few hundred MB doesn't tell us anything. You
> can use the anonmyzing option that will hide URLs.

should I do this with all add-ons, themes etc disabled ?

	Loic
	Comment 5 • 7 years ago

(In reply to Sammerb from comment #4)
> should I do this with all add-ons, themes etc disabled ?

The best is to measure and save memory with a new profile:
https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles

You can create a testing profile and save memory log.

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

Sammerb, have you had a chance to retest? Also it would be helpful if you could test in a more recent version of Firefox to see if the problem has been fixed in more recent releases -- our next ESR is based on 52, currently dev edition.

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

Closing for now, feel free to reopen if your problem persists.