1.5 GB Private Bytes?

[malinois 165]

Hi

I have a general quick question in regards to Web Root Secure Anywhere Essentials.

I notice in using either Process Hacker or Process Explorer it states that

WRSA.exe is at 1.5 GB private bytes.

Isn't that quite high?

Thank you in advance.

[Dermot7]

Are you sure it's not e.g. 15000 Kilobytes?

[malinois 165]

Hi

It does state 1.5GB.

Thanks!

Originally Posted by Dermot7

Are you sure it's not e.g. 16000 Kilobytes?

[Dermot7]

Ok sorry, hopefully TripleHelix PrevxHelp or someone will be along to help.

P.S. Have you tried a fresh install (without exporting/importing settings) to see if any different?

[malinois 165]

Hi

This number seems to increase while watching streaming movies on Netflix. After closing down the browser the number does not go down (not released)

I have not tried a fresh install. I just installed this the other day.

Thanks.

Originally Posted by Dermot7

Ok sorry, hopefully TripleHelix PrevxHelp or someone will be along to help.

P.S. Have you tried a fresh install (without exporting/importing settings) to see if any different?

[Triple Helix]

Originally Posted by malinois 165

Hi

This number seems to increase while watching streaming movies on Netflix. After closing down the browser the number does not go down (not released)

I have not tried a fresh install. I just installed this the other day.

Thanks.

Hello and Welcome to the Prevx & Webroot SecureAnywhere Support Forum,

Private Bytes is Virtual Memory and the Working Set is Actual Memory(RAM) I have seen my Private Bytes go into the hundreds but that high only PrevxHelp would know why!

TH

This is mine at the moment!

[malinois 165]

Hi!

Thank you for the welcome.

I've rebooted and currently watching a 2nd title on Netflix. This time the private byte usage is much lower. Enclosed a screen shot.

I'll keep my eye on it. Just wondering why it shot up so high and stayed there.

Thank again.

(ss from Process Explorer this time)

Originally Posted by Triple Helix

Hello and Welcome to the Prevx & Webroot SecureAnywhere Support Forum,

Private Bytes is Virtual Memory and the Working Set is Actual Memory(RAM) I have seen my Private Bytes go into the hundreds but that high only PrevxHelp would know why!

TH

This is mine at the moment! Attachment 233524

[Triple Helix]

Originally Posted by malinois 165

Hi!

Thank you for the welcome.

I've rebooted and currently watching a 2nd title on Netflix. This time the private byte usage is much lower. Enclosed a screen shot.

I'll keep my eye on it. Just wondering why it shot up so high and stayed there.

Thank again.

(ss from Process Explorer this time)

That looks better and myself I don't care for Process Hacker as you can see I like Process Explorer!

TH

[Techfox1976]

While I can't say absolutely for sure why it shot up that high, I can make a few educated guesses.

Private bytes is just what the program or a library loaded in it asked for as memory that will not include shared memory space (DLLs). This is just asked-for, not necessarily used. Windows memory management will still tell the program to bugger off if it a: can't get that much at the time, or b: needs it back later and the program is not actively using it at the time.

The "or a library loaded in it" is a critical part. Any process can have a library injected into it without it actively requesting such. WSA is no different, it just protects itself against injection by potentially-malicious stuff. But stuff that is known-good can still inject. If that known-good DLL allocates a lot of RAM for some reason, it will show up under the program in question.

So it could be WSA, or it could be a DLL auto-load, or something else injected. And it shouldn't actually impact anything, because it's nothing but headroom (Max headroom, mind you).

[PrevxHelp]

Originally Posted by Techfox1976

While I can't say absolutely for sure why it shot up that high, I can make a few educated guesses.

Private bytes is just what the program or a library loaded in it asked for as memory that will not include shared memory space (DLLs). This is just asked-for, not necessarily used. Windows memory management will still tell the program to bugger off if it a: can't get that much at the time, or b: needs it back later and the program is not actively using it at the time.

The "or a library loaded in it" is a critical part. Any process can have a library injected into it without it actively requesting such. WSA is no different, it just protects itself against injection by potentially-malicious stuff. But stuff that is known-good can still inject. If that known-good DLL allocates a lot of RAM for some reason, it will show up under the program in question.

So it could be WSA, or it could be a DLL auto-load, or something else injected. And it shouldn't actually impact anything, because it's nothing but headroom (Max headroom, mind you).

A perfect response

Even though it does look higher than normal, you shouldn't be worried - if the system did require the resources back, WSA will happily hand them over.

[malinois 165]

Thank you for the explanation. I understand it now.

Ram usage has remained low since that time.