We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

What are cached window objects in the about:memory tab in firefox?

  • 5 antwurd
  • 1 hat dit probleem
  • 2 werjeftes
  • Lêste antwurd fan Shadow110

more options

Hi, I have multiple test pages, and when i refresh multiple .html page one after the other, i can see the memory growing. When i hit the measure button in the about:memory tab, I see the active window object for my current html page, but i also see a child node called cached with window objects from the previous loaded .html pages.

Could someone help me understand this behavior? Thanks

Hi, I have multiple test pages, and when i refresh multiple .html page one after the other, i can see the memory growing. When i hit the measure button in the about:memory tab, I see the active window object for my current html page, but i also see a child node called cached with window objects from the previous loaded .html pages. Could someone help me understand this behavior? Thanks

Alle antwurden (5)

more options

This would be cached parts of the pages kept in memory until no longer needed or is flushed by amount of more tabs opened . This is normal behavior of all browsers and ram.

more options

Is there any way to avoid caching parts of pages after navigating away from it?

more options

muthu90ec said

Is there any way to avoid caching parts of pages after navigating away from it?

Firefox should not be caching pages after navigating away from them. If you leave a tab open and the updates will cache the new changes.

What is it you are trying to achieve please. ??

more options

Yes that's what i thought, but I have two pages for eg: localhost:8080/some/path/page1.html localhost:8080/som/path/page2.html Note page1.html and page2.html loads similar js resources.

Navigating away from page1.html to page2.html and in the about:memory page i still can see cached window objects int page1.html, i am trying to understand why that would be the case

more options

That was explained in my 1st answer. Go to 30 more pages and it will probably be gone and replaced with other info.

If your not having a problem. You should be able to do your own research on this.

Please let us know if this solved your issue or if need further assistance.