Originally Posted by Screemer
Great, thanks for the swift reply..
No worries :)
Originally Posted by themushroom
Originally Posted by MrAlex
Does this memory usage make Waterfox unstable? I don't think I'll be able to release a fixed version in time as 35.0.1 is already massively late and I'd like to release it tomorrow. If it's usable for now I'll seed the patch, if not I'll have to delay. Thanks for your report!
Not so much "unstable" in the browser or the computer, but definitely sludgy on both counts. It takes a few hours to get that full, it's not an immediate issue. The behavior when it reaches critical mass is that it spins the hard drive for several minutes (a cache swap Windows does when a computer doesn't have enough RAM?), it takes up to a minute to go between tabs, and sometimes the program will go into "not responding" mode while sometimes it doesn't. Waterfox does NOT crash the machine or lock up, happily, but the two choices when this overload happens are to either wait it out or use Task Manager to shut it down which flushes everything out (merely closing the program keeps it resident for a minute or three longer). Then when Waterfox is relaunched everything's peachy again until the next time.
Ah right okay thanks for the info!
Could anyone please test the update for 35.0.1 for me:
Go to about:config, Right click anywhere New > String
And then name of the string: app.update.url.override
And the value of the string: https://www.waterfoxproject.org/update/test/win/update.xml
Then just go to About Waterfox and apply the patch :)