Norton for Mac

[Lee_G]

The AV scan engine does appear busy, but it's hard to tell much else.  Can you run the "Gather Support Information" command from the NAV Help menu?  I'll send a private message with an email address where you can send it.

[WJDIV]

HELP!  SymDemon is consuming between 95% and 184% of my CPU.  I have a MacBook AIr 1.8 GHz Intel Core i7 runnign Mac OS X, version 10.7.4.  The computer's fan is running constantly.  I have tried solutions mentioned in previous posts to no avail.  Attache dis a sample of SymDaemon.  Any help would be appreciated.

[Lee_G]

Can you follow the instructions here to generate some Symantec Info (you don't have it in the Help menu in your version):

    http://www.symantec.com/business/support/index?page=content&id=TECH13476

I'll send a private message with an email address where you can send the zip or txt file the tool creates.

One question, in the meantime:  were you doing a manual scan when this occurred, and if so did you include any Time Machine volumes?

[Lee_G]

Actually, I misread the OS version, you should have the Help menu "Gather Support Information" command (I'm assuming you have NAV 12 or NIS 5, earler versions are not Lion compatible).

[tikves]

I have a similiar problem.

SymDaemon is taking up to 400 MB of Real Memory.

Here is the text file from Activity Monitor.

[LV]

Lee,

Please HELP!  SymDemon is consuming more than 100% of my CPU.  I have a MacBook 2 GHz Intel Core 2 Duo running OS X, version 10.7.4.  The computer's fan is running constantly. The CPU gets so bogged down that the computer is slow as hell - very frustrating. Attached is a sample of SymDaemon.  Any help would be appreciated!

Thanks and Regards,

LV

[ryan_mcgann]

This would appear to be a bug in Norton Firewall 4.1. I can't reproduce it on my machine, but it looks like the Norton DeepSight feature is running a liitle amok.

Also, you are running an old version of the product on Mac OS X 10.7. Norton Firewall 5.0 is the latest version, and it is the only version that is supported on Mac OS X 10.7. The good news is, this bug definitely cannot exist in Norton Firewall 5, because that the section of code that is running amok is completely gone in Norton Firewall 5.

How did you obtain the product, and when did you purchase it?