Guest User!

You are not Sophos Staff.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 74 replies
  • Subscribers 6 subscribers
  • Views 49593 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

System becomes unresponsive

Chogidog

I tried the AV out and found it had negative effects on my system. I have a Macbook Pro 3,1 with a 2.4ghz processor, 4gb of ram and a 500gb hd running 10.6.4. 

I noticed that start ups had become longer and icons on my desktop weren't immediately there, instead there were placeholder dashed rectangles. 

I attempted 2 separate scans. Both resulted about the same. My MBP became unresponsive, the items remaining count stopped and the CPU temperature dropped from an elevated working temp to a lower idle temp. I wasn't able to check through the activity monitor due to the unresponsiveness. Both times I had to press and hold the power button to shut down because clicking restart didnt respond.

Anyone else having this problem?

:1000063


This thread was automatically locked due to age.
Parents
  • 0

    Briefly, for the record:

    • in some environments without Boot Camp, the computer may stop responding at login time (after the user enters credentials, before the computer becomes usable) 
    • for a user whose home directory is served via AFP the computer may stop responding soon after a manual scan begins

    — both cases requiring a forced stop (press and hold the power key) or a forced restart (command-control-power).

    I'll post details separately in around two weeks' time, possibly sooner — I shouldn't broaden this already long topic.

    FWIW I sense a generic bug that causes things to stop responding in a variety of environments, for a minority of users. 

    Focus on something within a Boot Camp environment may yield a workaround, possibly an exclusion, for that environment but ultimately I think that we (users) need Sophos Anti-Virus to:

    • handle, more gracefully, situations that are novel or anomalous
    • never contribute to a forced stop/restart situation.

    Side note: does anyone know what happens, technically, when command-control-power is keyed? It seems more graceful than a sudden stop (disk activity is audible for a while before the stop, before the startup chime) but I have never found an Apple article on the subject.

    :1000313
Reply
  • 0

    Briefly, for the record:

    • in some environments without Boot Camp, the computer may stop responding at login time (after the user enters credentials, before the computer becomes usable) 
    • for a user whose home directory is served via AFP the computer may stop responding soon after a manual scan begins

    — both cases requiring a forced stop (press and hold the power key) or a forced restart (command-control-power).

    I'll post details separately in around two weeks' time, possibly sooner — I shouldn't broaden this already long topic.

    FWIW I sense a generic bug that causes things to stop responding in a variety of environments, for a minority of users. 

    Focus on something within a Boot Camp environment may yield a workaround, possibly an exclusion, for that environment but ultimately I think that we (users) need Sophos Anti-Virus to:

    • handle, more gracefully, situations that are novel or anomalous
    • never contribute to a forced stop/restart situation.

    Side note: does anyone know what happens, technically, when command-control-power is keyed? It seems more graceful than a sudden stop (disk activity is audible for a while before the stop, before the startup chime) but I have never found an Apple article on the subject.

    :1000313
Children
No Data