Guest User!

You are not Sophos Staff.

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

Complete lockups due to Sophos Anti-Virus

Sometimes (about 2-3 times a month) my Macbook Air displays the spinning beach ball in more and more applications until everything hangs and I have to restart. This happens on my family's other Macs, too. A few months ago I noticed that everytime this happens, the Sophos icon in the menu bar indicates that Sophos is currently updating. I checked my theory and indeed, every single time one of the Macs crashes, Sophos is doing an update. This cannot be a coincidence.

I then tried to find out what exactly happens and why all apps are crashing. I found out that they cannot access the hard drive anymore. They continue to work fine as long as they do not access the disk. As soon as they try to load anything from the disk, they stall and display the beach ball.

Usually, everytime an app wants to access the hard drive, Sophos intercepts this attempt, scans the file for viruses first and then allows the app to read it. I believe that there's some kind of bug in the Sophos update code that sometimes (usually updates work fine) makes Sophos intercept hard drive accesses without ever scanning and unblocking them.

This serious bug was affecting the commercial Sophos Anti-Virus 7 which my university used till last month, and it still affects Sophos Anti-Virus 8. It also affects the home edition of Sophos Anti-Virus 8 which all my family members use. We all use Mac OS X Lion and regularly update it.

The log files on a crashed computer look like this:

27.06.12 10:48:38,372 installer: Package Authoring Error: Infinite loop between <choice> attributes and mixed state aborted.
27.06.12 10:48:39,439 installer: Configuring volume "Mac OS X"
27.06.12 10:48:39,452 installer: Free space on "Mac OS X": 10,32 GB (10324697088 bytes).
27.06.12 10:48:39,452 installer: Create temporary directory "/var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T//Install.4959z5UUG"
27.06.12 10:48:39,460 installer: IFPKInstallElement (19 packages)
27.06.12 10:48:39,866 installd: PackageKit: ----- Begin install -----

The next entries happen after the restart.

:1007915


This thread was automatically locked due to age.
Parents
  • Ok, actually Sophos did automatically update again after the restart and it worked:

    28.06.12 13:48:25,988 installer: Package Authoring Error: Infinite loop between <choice> attributes and mixed state aborted.
    28.06.12 13:48:27,094 installer: Configuring volume "Mac OS X"
    28.06.12 13:48:27,109 installer: Free space on "Mac OS X": 10,97 GB (10969858048 bytes).
    28.06.12 13:48:27,109 installer: Create temporary directory "/var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T//Install.485GLBKM3"
    28.06.12 13:48:27,116 installer: IFPKInstallElement (19 packages)
    28.06.12 13:48:27,441 installd: PackageKit: ----- Begin install -----
    28.06.12 13:48:54,678 installd: Installed "Sophos Anti-Virus" ()
    28.06.12 13:48:54,843 installd: PackageKit: ----- End install -----
    28.06.12 13:48:55,479 installer: Removing temporary directory "/var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T//Install.485GLBKM3"
    28.06.12 13:48:55,483 installer: Finalize disk "Mac OS X"
    28.06.12 13:48:55,483 installer: Notifying system of updated components
    28.06.12 13:48:55,483 installer: **** Summary Information ****
    28.06.12 13:48:55,484 installer:   Operation      Elapsed time
    28.06.12 13:48:55,484 installer: -----------------------------
    28.06.12 13:48:55,484 installer:        zero      0.01 seconds
    28.06.12 13:48:55,484 installer:        disk      0.02 seconds
    28.06.12 13:48:55,484 installer:     install      28.36 seconds
    28.06.12 13:48:55,484 installer:     -total-      28.38 seconds

    So the version numbers I gave you in the last posting were the version numbers *after* the update. I'm sorry, I hadn't realized Sophos had already updated itself again, this time successfully.

    I understand it's very difficult to debug something if the bug is not always reproducible, but I'd be very happy if this bug could be corrected. Since the whole Mac stops working, one often loses some unsaved data.

    :1007941
Reply
  • Ok, actually Sophos did automatically update again after the restart and it worked:

    28.06.12 13:48:25,988 installer: Package Authoring Error: Infinite loop between <choice> attributes and mixed state aborted.
    28.06.12 13:48:27,094 installer: Configuring volume "Mac OS X"
    28.06.12 13:48:27,109 installer: Free space on "Mac OS X": 10,97 GB (10969858048 bytes).
    28.06.12 13:48:27,109 installer: Create temporary directory "/var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T//Install.485GLBKM3"
    28.06.12 13:48:27,116 installer: IFPKInstallElement (19 packages)
    28.06.12 13:48:27,441 installd: PackageKit: ----- Begin install -----
    28.06.12 13:48:54,678 installd: Installed "Sophos Anti-Virus" ()
    28.06.12 13:48:54,843 installd: PackageKit: ----- End install -----
    28.06.12 13:48:55,479 installer: Removing temporary directory "/var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T//Install.485GLBKM3"
    28.06.12 13:48:55,483 installer: Finalize disk "Mac OS X"
    28.06.12 13:48:55,483 installer: Notifying system of updated components
    28.06.12 13:48:55,483 installer: **** Summary Information ****
    28.06.12 13:48:55,484 installer:   Operation      Elapsed time
    28.06.12 13:48:55,484 installer: -----------------------------
    28.06.12 13:48:55,484 installer:        zero      0.01 seconds
    28.06.12 13:48:55,484 installer:        disk      0.02 seconds
    28.06.12 13:48:55,484 installer:     install      28.36 seconds
    28.06.12 13:48:55,484 installer:     -total-      28.38 seconds

    So the version numbers I gave you in the last posting were the version numbers *after* the update. I'm sorry, I hadn't realized Sophos had already updated itself again, this time successfully.

    I understand it's very difficult to debug something if the bug is not always reproducible, but I'd be very happy if this bug could be corrected. Since the whole Mac stops working, one often loses some unsaved data.

    :1007941
Children
No Data