The old "low on memory" issue

This sounds utterly bizarre to me. I can't fathom a time you would ever need a 32GB page file let alone 48!?

Windows is terrible at working without it that's why I'd recommend leaving it at default, I'd wager that whatever fixed amount you set it to you'll run out of memory at some point if you multitask a lot.

My point ultimately was that the more physical memory you have the less of a page file you need and setting page file to equal your physical memory amount does the opposite so it's poor advice anyway. I don't know what the magic number to set your page file to is because it's dynamic depending on what you're doing with your system, that's why I'd just let Windows have access to all of the storage capacity it needs.
 
Last edited:
that is definately abnormal

Handles can leak memory as well (I have seen this with Bitdefender, IE, NIC drivers)

RAMmap is useful

Yes Avira is rubbish for leaks, their real-time tracker (plan to change to sophos)
otherwise it is largely multi-tasking and gradually having more and more tabs open on firefox, and ... if I have to use chrome
(I mentioned RAMmap a couple of posts earlier :) )

I need to try that multi-tasking test myself , for those that had not yet dared.
 
I run Avira and Firefox (for years!) - no issues and am a heavy multi tasker

Typically: Photoshop, VS, email, WOT, Word, FileZilla and 2 or 3 Browsers etc
 
for fun -
The monstrosity that is Avira = 1GB
+ evil twin chrome (saved session with 6 tabs) ~ 5GB
+ 3 of firefoxes/waterfoxes (20 tabs each) ~ 5GB

avira_monster_zpspftvtomt.png~original
 
You did try updating the killer network driver, right?

Thanks I do not have a killer NIC, and driver memory reported from RAMmap does not seem to show an issue from nic or wireless card.

I don't think Virtual Size is a helpful metric

You are right Private bytes is probably what I should have highlighted to represent contribution to commit charge,
difference is the dll's and the memory they may have allocated, in theory;
and chrome looks less bad if all the chrome processes share many dll's.

I have used ff for many years but only just discovered the about:memory option which does actually give a run down per tab eg

4,095.94 MB (100.0%) -- address-space
├──2,492.75 MB (60.86%) ── free [575]
├──1,311.25 MB (32.01%) -- commit
│ ├────804.39 MB (19.64%) -- private
│ │ ├──615.32 MB (15.02%) ── readwrite [2208]
│ │ ├──184.80 MB (04.51%) ── readwrite+writecombine [42]
│ │ └────4.26 MB (00.10%) ++ (5 tiny)
│ ├────319.57 MB (07.80%) -- mapped
│ │ ├──239.96 MB (05.86%) ── readonly [123]
│ │ ├───53.72 MB (01.31%) ── readwrite+writecombine [39]
│ │ └───25.89 MB (00.63%) ++ (2 tiny)
│ └────187.28 MB (04.57%) -- image
│ ├──102.05 MB (02.49%) ── execute-read [198]
│ ├───80.91 MB (01.98%) ── readonly [426]
│ └────4.32 MB (00.11%) ++ (3 tiny)
└────291.94 MB (07.13%) -- reserved
├──267.91 MB (06.54%) ── private [1650]
└───24.03 MB (00.59%) ++ (2 tiny)

...

├────5.61 MB (01.07%) ++ top(http://security.stackexchange.com/questions/97064/is-gmail-to-gmail-still-insecure-why, id=1447)
│ ├────5.50 MB (01.05%) ++ top(http://stackoverflow.com/questions/1984186/what-is-private-bytes-virtual-bytes-working-set, id=3105)
│ ├────5.30 MB (01.01%) ++ top(http://www.imdb.com/title/tt20
│ └────5.25 MB (01.00%) ++ top(http://superuser.com/questions/7273...rted-by-windows-task-manager-much-higher-than, id=73)

 
I've had this error a couple of times since yesterday, despite the dialogue box requesting to close chrome, if i go to Task manager its actually the netflix app that is using 6GB of ram for some reason, doesn't do it all the time though. Not sure whats changed.
 
Nonpaged pool from rammap 350MB (so I do not think drivers/kernel are bad)
Number of handles - peak handles from process Explorer for waterfox(biggest process) 1500
 
Thanks, I identified process creating the handles, and seems to commonly do this

C:\Windows\SwUSB.exe "Switch USB2.0/USB3.0 for WinXP SP2+ ~ Win8"

have disabled service and will see what happens, this process for me, is not large ~5MB private bytes, but is creating the handles.

In my case it was the runSW.exe application, started by the runSwUSB service, that took more than 8 GB of memory. I found it by adding Handles and GDI objects in the task manager view, as suggested by rseiler and others above. It seems to have come with the recent installation of an Asus USB wireless-ac dongle. Stopping it does not seem to cause any problems.
 
Hi Guys,

Just wanted to come back and comment saying that both allowing windows to control my pagefile and setting it to 16gb both worked for me.

I am battling with another issue at the moment - PC freezes because wlanext.exe is spiking my memory usage to 100% reaching up to 10gb used for 1-2 seconds every 5-10minutes... nightmare!

Thank you all for your replies!

wlanext_exe_90_memory.jpg
 
Last edited:
A few hits on google for that problem - assuming it isn't related to the Killer NIC then doesn't look like anyone has solved it - 1-2 reported success after reinstalling Windows 10 but others ended up going back to 8 or 7.
 
Yeah been working on this issue all day, not much on google about it. I seem to stay online if I just end the process but I don't see that as a permanent solution really. Will keep going with it!
 
Back
Top Bottom