• Notice regarding image hosts and attachments. See here.

Obscenely high memory usage?

The problem seems to be with how Killer's drivers interact with the windows network monitor thingymabob. All is good though now, non-paged pool is at 135mb this morning which is a relief! Fire Wizard thankyou for pointing me towards RAMMap as it led me to the solution!
 
arfoll said:
That sounds more logical than firefox ;-) Nice one and thanks for coming back, always handy to know!



Another example of why end users should never be using aurora! I don't understand why mozilla/chromium are pushing users towards this so much these days... Running nightly builds is never a good idea unless you're a dev of that particular SW....
Click to expand...

Not necessarily a developer of firefox but work as a web developer on a freelance basis while at uni. So I use it to test how sites run on new builds along with programming new features into web apps using the new features only found in nightly builds. That way I can roll out a new feature on the site the second the stable release with that feature is out.

But as a general rule I don't advise people to run nightly builds as their main browser, I even use firefox stable as my daily driver. Aurora for when I need it.

Also agree, I have no idea why chromium and Mozilla push new users to use the nightly builds. In general people now days think alpha/beta is just a early version of a program with more stuff to play with and expect no bugs or issues... I blame all these early alpha/beta game releases tbh minecraft for one.
 
You must log in or register to reply here.
Back
Top Bottom