I feel this too... Often I open up a firefox tab to add a new banknote or so, and read on it on another tab. When I return back, the tab seem to be frozen and doesn't respond for quite sometime... The numista pages take up a lot of memory when left alone over time.
Quote: "Chatterjee_Soubhik"I feel this too... Often I open up a firefox tab to add a new banknote or so, and read on it on another tab. When I return back, the tab seem to be frozen and doesn't respond for quite sometime... The numista pages take up a lot of memory when left alone over time.
Ditto. I've had the same issue
Status changed to Started(Xavier, 6-Nov-2020, 04:24 pm)
Quote: "Xavier"I made some adjustments (only with the new design). Could you please advise whether you still experience the same issue?
Thank you for maintaining and improving the site.
It looks like there is still a memory problem. I left three Numista search results tabs for about three hours and there was roughly a 20% increase in memory usage. Usage is volatile, it can go up and down 5% in a minute, but there is a clear upward trend.
This is just memory use for numista.com. The memory usage for the iframes shown on Numista and for my other browsing isn't included.
I'm running the nightly build of Firefox with a new feature, about:processes, which gives the memory use for each process, and I've enabled an experimental feature that puts each domain in a separate process. That lets me directly monitor the memory usage of numista.com instead of looking at the overall Firefox usage and guessing how much is Numista. I believe about:processes will ship and users will be able to enable site isolation in Firefox 84 on December 15th. about:processes didn't give this much detail when I started this thread.
Could you please more details about what you observe as memory consumption and which flag you activated for monitoring?
Please also confirm whether you are testing with the old design or the new design.
I did a test by looking at about:performances in Firefox, and the memory consumption looks quite low even after 3 hours.
I am testing with the new design of Numista. I see memory increases in both Firefox and Chrome.
My actual Firefox memory numbers don't represent real-world consumption as I'm running a testing build designed to look for Firefox memory leaks which results in a much higher memory use.
Site isolation in Firefox is Project Fission. It is expected it will be possible to enable it in the release version of Firefox in December, and about:processes will be in the release version as well at that time.
Unfortunately about:performance in Firefox doesn't correctly allocate all memory usage to the correct site, but running each site in a separate process does.
To test in Chrome you can use the Task Manager (Menu / More tools / Task manager). What I am seeing is memory use goes generally up for a minute or so, gaining 5-7 MB, and the drops all but a fraction of a MB. Over about a half hour the base went from around 93MB to around 109MB. (I'm actually using Chromium on Linux.)
The 17:04 is near the high point of the cycle, but I haven't seen it below 110MB for the last 15 minutes.