node and Windows Defender?
2,382 views
Skip to first unread message
Thomas Shinnick
Jan 9, 2012, 7:13:21 PM1/9/12
to nod...@googlegroups.com
Yes, I'm paranoid, and I flinch when the lights merely flicker, and am constantly noticing things preternatural that others shrug off, but....
Has anyone else noticed that MS's Windows Defender pegs out a cpu for a couple seconds whenever node.exe is executed from command line? Even when running an empty file? And still only for 2-3 seconds total, even when executing several (20) times in a bunch? But if alternating with other programs then Windows Defender will re-peg for a couple seconds for each execution of node.exe?
What I'm worried about is that Windows Defender might be freaking out on each execution of node, and that that might be creating 'apparent' performance problems. I suppose not a problem with the usual daemon/server setup, but perhaps also a worry if spawning copies of itself, in addition to command line usage hits (like just running npm)?
Has anyone else noticed that MS's Windows Defender pegs out a cpu for a couple seconds whenever node.exe is executed from command line? Even when running an empty file? And still only for 2-3 seconds total, even when executing several (20) times in a bunch? But if alternating with other programs then Windows Defender will re-peg for a couple seconds for each execution of node.exe?
What I'm worried about is that Windows Defender might be freaking out on each execution of node, and that that might be creating 'apparent' performance problems. I suppose not a problem with the usual daemon/server setup, but perhaps also a worry if spawning copies of itself, in addition to command line usage hits (like just running npm)?
mscdex
Jan 9, 2012, 7:53:52 PM1/9/12
to nodejs
On Jan 9, 7:13 pm, Thomas Shinnick <tshin...@gmail.com> wrote:
> Has anyone else noticed that MS's Windows Defender pegs out a cpu for a
> couple seconds whenever node.exe is executed from command line? Even when
> running an empty file? And still only for 2-3 seconds total, even when
> executing several (20) times in a bunch? But if alternating with other
> programs then Windows Defender will re-peg for a couple seconds for each
> execution of node.exe?
Do you have it set to scan every program as they start or some kind of
> Has anyone else noticed that MS's Windows Defender pegs out a cpu for a
> couple seconds whenever node.exe is executed from command line? Even when
> running an empty file? And still only for 2-3 seconds total, even when
> executing several (20) times in a bunch? But if alternating with other
> programs then Windows Defender will re-peg for a couple seconds for each
> execution of node.exe?
"resident shield" type of feature activated? If so, try temporarily
disabling and see if that affects it any.
C. Mundi
Jan 9, 2012, 8:06:42 PM1/9/12
to nod...@googlegroups.com
Ok I'm going to do something really naive. Feel free to laugh.
Windows Defender is a Microsoft Product. Microsoft is a sponsor of node.js. So...maybe they'll fix it?
:)
--
Job Board: http://jobs.nodejs.org/
Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nod...@googlegroups.com
To unsubscribe from this group, send email to
nodejs+un...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
Glenn Block
Jan 9, 2012, 9:08:17 PM1/9/12
to C. Mundi, nod...@googlegroups.com
Duly noted. I will talk to our test team to check it out.
Cheers
Glenn
Sent from my Windows Phone
Cheers
Glenn
Sent from my Windows Phone
From: C. Mundi
Sent: 1/9/2012 5:06 PM
To: nod...@googlegroups.com
Subject: Re: [nodejs] Re: node and Windows Defender?
Thomas Shinnick
Jan 9, 2012, 9:59:16 PM1/9/12
to nod...@googlegroups.com
I hadn't noticed that Windows Defender _does_ have a Control Panel item after all...
Control Panel / Windows Defender / Tools / Options / Excluded files and folders
Add "C:\Program Files (x86)\nodejs\node.exe"
Save
Interestingly, there were no other items in the 'excluded' list, and yet this is the first time I'd really noticed the behavior. Strange that MS would consider things like Cygwin and friends okay, but node not. Or maybe "not yet"? Perhaps there is an occasional less-than-daily scan to satisfy it that mumblebot.exe is not a threat and it fills in a list of 'okay-to-execute' files?
Thanks for the push...
Control Panel / Windows Defender / Tools / Options / Excluded files and folders
Add "C:\Program Files (x86)\nodejs\node.exe"
Save
Interestingly, there were no other items in the 'excluded' list, and yet this is the first time I'd really noticed the behavior. Strange that MS would consider things like Cygwin and friends okay, but node not. Or maybe "not yet"? Perhaps there is an occasional less-than-daily scan to satisfy it that mumblebot.exe is not a threat and it fills in a list of 'okay-to-execute' files?
Thanks for the push...
Reply all
Reply to author
Forward
0 new messages