This discussion is locked
robrecord
Level 1 (5 points)

Q: Random freezing from Snow Leopard - total lock-up for about 30 seconds

I am having random freezes like the authors of many recent topics on this forum. From the number of 'views' on their threads, it seems that many other users have the same problem.

These are not like any other freezes I have ever had - usually when the beach ball shows, it still allows me to show the dock, move windows etc... but these freezes bring everything to a halt.

Since this problem first started for me the say I upgraded, and seems to be the same (from what I can tell) for other users who reported this, does anyone know if there is something about snow leopard that uses the hardware differently? So that whereas under leopard (32-bit) there may not have been a fault, but on switching to 10.6 a problem could reveal itself?

Mac Pro 1,1 2007, 2x 2.66 GHz Dual-Core, Mac OS X (10.6), 4 x 1Gb Apple RAM, 1x 500Gb WD Caviar, 2x Optiarc Superdrive, GeForce 7300 256Mb, Dual monitors

Posted on Sep 3, 2009 2:38 AM

Close
robrecord

Q: Random freezing from Snow Leopard - total lock-up for about 30 seconds

  • All replies
  • Helpful answers

first Previous Page 36 of 36

  • by @martinlabelle,

    @martinlabelle @martinlabelle Nov 3, 2010 9:22 AM in response to robrecord
    Level 1 (0 points)
    Nov 3, 2010 9:22 AM in response to robrecord
    I think that this is a problem with Adobe CS4 and the new Flash Player, and I think it centers around the clipboard memory. I think what is going on is that there is a shared clipboard, however the owner of that memory is undefined according to the console (OSX). I suspect that Adobe has created a shared clipboard space between its applications and the interaction with the recent flashplayer is causing ownership issues.

    The error happens when a CS4 app (possibly CS5, untested with me) quits. I assume it checks to see if other CS apps are running; if not it releases the memory that the clipboard uses. With the new update to flash player, it appears to the OS that dreamweaver is releasing memory it was not allocated; This is a security problem from the perspective of the kernel.

    Just a theory, the only fix will be with adobe, I suspect.
first Previous Page 36 of 36