Guest User!

You are not Sophos Staff.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 74 replies
  • Subscribers 6 subscribers
  • Views 49571 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.
  • 0

    ibell63,

    Thanks for the help.

    But now I'm getting a different message.

    When I type:

    sweep /Volumes/BOOTCAMP  -dn >> /Users/<brianarmour>/Desktop/SweepLog.txt

    I get:

    -bash: /Users/: Is a directory

    Any thoughts?

    :1000244
  • 0

    Ok, this is getting a lot closer to working now, but there's still two problems that I can see:

    This is what you entered:

    sweep /Volumes/BOOTCAMP  -dn >> /Users/<brianarmour>/Desktop/SweepLog.txt

    First, you have a space between ">>" and "/Users/".

    Second, it shouldn't actually have the "<" and ">" characters around your username, we just used that to indicate that's where text needed to be added.

    So I suggest you try this:

    sweep /Volumes/BOOTCAMP -dn>>/Users/brianarmour/Desktop/SweepLog.txt

    and if that doesn't work:

    sweep /Volumes/BOOTCAMP -dn>>/Users/Brian/Desktop/SweepLog.txt

    The reason why I said "Brian"  instead of "brianarmour" is because sometimes OS X uses only your first name and sometimes it uses your full name.

    Command prompts are very picky about spelling and spaces and such things.

    Thanks in advance.

    :1000246
  • 0

    ibell63,

    Awesome, its working now. Thanks for the help.

    Marf,

    I sent you those panic reports

    :1000248
  • 0

    Marf,

    The terminal sweep completed with no issues. 

    61005 files swept in 18 minutes and 38 seconds.
    17 errors were encountered.
    No viruses were discovered.

    Would you like the sweep log?

    :1000252
  • 0

    While we're waiting for Marf, I have annother suggestion.

    Since the issue seems like it may or may not be related to scanning compressed files, could you try scan with the command prompt explicitly asking to scan compressed files?

    sweep -archive /Volumes/BOOTCAMP -dn>>/Users/brianarmour/Desktop/SweepLogCompressed.txt

    OR

    sweep -archive /Volumes/BOOTCAMP -dn>>/Users/Brian/Desktop/SweepLogCompressed.txt

    The "-archive" option tells it to scan all supported archives.

    I put a different name for the log file so it doesn't overwrite the old one, so on your desktop you should have SweepLog.txt and SweepLogCompressed.txt after you run these.

    Please choose whatever one worked for you last time in regards to the username.

    Remember if it hangs, don't depend on the log file, make note of the name of the file and especially the extension.

    Thanks!

    Ian

    :1000255
  • 0

    Ian,

    Scanning now.  I've had the terminal window up and positioned so that i can monitor what its up to and notice if it hangs. So if it does, I should catch it.

    Speak of the devil..

     it's currently hung on  objects.xib

    I'l post up when it finishes or I restart. 

    Whichever comes first

    Brian

    :1000256
  • 0

    So it was after a restart.

    It hung on objects.xib and never progressed past it.

    I saved the dialog in terminal up to where it stopped in addition to the log the scan saved.

    :1000259
  • 0

    In answer to your question Marf,

    My BOOTCAMP partition is Windows XP Pro.

    Rand

    :1000261
  • 0

    So, all of a sudden after a whole bunch of repititions, I am no longer able to make my machine hang.

    Before it stopped crashing, I had inconsistent results as to what file type was causing the freezes / panics.

    On two occasions where I was able to find out which file it stopped on, these were the files it stopped on:

    SourceHTMLTokenizer.re2js

    C:\Program Files/iTunes/iTunes.Resources/fr.lproj/Localizable.strings

    I have the full file path for the second file, because on that scan I used the -ns option.

    Annother thing I did notice when it did stop freezing was that almost every time, right before it froze, the menu bar icon indicated sophos was trying to update at the time, this leads me to believe that there may be an issue with auto update interfering with the local scan working correctly.

    I have stopped testing this at this point in time.  If I happen to run into more problems through normal use, I will post here.

    Apart from these minor temporary bugs, thanks, Sophos for making a decent free antivirus available for the mac, it couldn't have come at a better time.

    :1000263
  • 0

    Hi,

    Chogidog - thank you for the logs I can confirm that we have received those logs.

    On a wider note, thank you all for the feedback and testing you have been doing so far, this has helped us. 

    Support and Development are currently following a line of investigation and hope to have a clearer picture of the issue you are experiencing soon.

    As soon as I have further information on this I will update this post.

    Thanks

    Marf

    :1000273