(08-14-2015, 03:03 PM)BlueScreen Wrote: They even have a wiki page on how you can properly re-benchmark and reproduce the result.
https://github.com/gorhill/uBlock/wiki/F...-footprint
Now the contents In the Wiki page, Is exactly what I was referring to In my previous post.
It's one thing to document "high traffic webpages" (which denotes nothing at all), and another thing to actually specify the webpages In question.
Thank you for this, It Is of great help.
(08-14-2015, 03:50 PM)eclipse Wrote: RAM was made to be used.
Being used and being "exhausted" for all the wrong reasons, are completely different.
For example, If a given application was responsible for a memory leak, thus consuming all of the available/free Ram and then hitting the Page file (Virtual memory) leaving almost no memory available for critical tasks, then that's certainly a cause for concern- as this can cause significant system Instability and/or crashes.
Given Ram Is volatile (hence a reboot will discharge the Ram and revert to It's peak state), If the problematic application Is still there, memory will be consumed within a matter of minutes.