Norton360 has a long-standing buck that Norton has not fixed or found. The way an A/V program works, is it creates a virtual environment in RAM, a mini VM. Every time it encounters code it cannot determine is safe or not by other means, it will attempt to load and run that code. This process is amazing, and ingenious-- but not foolproof. Sometimes the mini VM gets stuck, get's lost in reiterations, and then begins to consume memory until it finally aborts internally, or you reboot the system.
Until Norton addresses this, the problem will not be fixed. I sit here with hundreds of N360.exe processes having been spawned, and N360 is the only A/V product I've used for years, because it is the best, other than this flaw. I have 16GB of RAM, a quadcore processor, running Windows 7.1 (not moving beyond that for logistical reasons), and the _only_ thing I've found that kinda/sorta works is to open the task manager, look at processes, then click on Resource Manager, and find the N360.exe process and click it (so it filters it). Usually within about 10 minutes-- suddenly Norton cleans itself up and voila, back to normal. I find that Norton only has this issue during idle periods. System is good at night, when I come in in the morning, it sometimes is in this altered state of either 2 N360.exe processes with one using an excessive amount of RAM, or (today for the first time), spawning hundreds of N360.exe processes, but not using lots of RAM.
Hope that helps somebody at Xfinity and Norton to fix this bug which is not at all difficult for them to catch by adding a couple of flags to the code, and monitoring. If windows can see an N360.exe process consuming Gigs of RAM, N360.exe can see it too.
... View more