Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Snow Leopard spinning wheel

Tex-Twil

Tex-Twil

macrumors 68030
Original poster
May 28, 2008
2,501
15
Berlin
Hi,
My SL was working perfectly until yesterday. I got my late 08 UMBP back from AppleCare without any replacement (see post here). They just run a kind of apple test suit on an external OSX, I guess they booted from a firewire disk.

Anyway, now I getting very often a system hang with a spinning wheel. When I try to repair permissions in the Disk Utility, the progress it stays like 10 minutes on the same place at the very beginning, then spinning wheel again :mad: then the system doesn't react. I can move the mouse that's all.


Any ideas ?

Thanks,
Tex
 
Are you getting an inordinate amount of pageouts? I'm just wondering if they opened it up, maybe one of the SODIMMs isn't seated properly and you're running on half the RAM you think you are. Just a long shot.
 
gr8tfly said:
Are you getting an inordinate amount of pageouts? I'm just wondering if they opened it up, maybe one of the SODIMMs isn't seated properly and you're running on half the RAM you think you are. Just a long shot.
Click to expand...
What is a page out ? and how can I check it ?

The memory part of $ system_profiler seems to be ok

Code: 
~ $ system_profiler | more
Memory:

    Memory Slots:

      ECC: Disabled

        BANK 0/DIMM0:

          Size: 2 GB
          Type: DDR3
          Speed: 1067 MHz
          Status: OK
          Manufacturer: 0x80CE
          Part Number: 0x4D34373142353637334448312D4346382020
          Serial Number: 0x475DC13E

        BANK 0/DIMM1:

          Size: 2 GB
          Type: DDR3
          Speed: 1067 MHz
          Status: OK
          Manufacturer: 0x80CE
          Part Number: 0x4D34373142353637334448312D4346382020
          Serial Number: 0x475DC18B

Btw, I let the repair permission run for more that an hour but it didn't move at all. Now I#m trying via command line but it doesn't look better.



Code: 
~ $ sudo diskutil repairPermissions /
Started verify/repair permissions on disk0s2 Macintosh HD
[   0%  ............................................... ]
 
I guess the quickest way to verify the RAM situation is to go to "About This Mac", from the :apple: menu.

You can check pageouts in Activity Monitor, under "System Memory"; or, if you're in Terminal, run "top". The summary will show you pageins & pageouts. The value in parenthesis is the number per second [of pageins or pageouts].

It's a longshot anyway, but if the machine's been opened who knows...
 
top says this
Code: 
MemRegegions: 6463 total, 825M resident, 14M private, 116M shared. PhysMem: 820M wired, 968M active, 244M inactive, 2032M used, 2064M free.
VM: 131G vsize, 1041M framework vsize, 47154[B](0) pageins[/B], 0[B](0) pageouts[/B].
So it also seems to be ok.

I think they didn't even open the Mac since they could not reproduce the screen problem I have.
 
Tex-Twil said:
top says this
Code: 
MemRegegions: 6463 total, 825M resident, 14M private, 116M shared. PhysMem: 820M wired, 968M active, 244M inactive, 2032M used, 2064M free.
VM: 131G vsize, 1041M framework vsize, 47154[B](0) pageins[/B], 0[B](0) pageouts[/B].
So it also seems to be ok.

I think they didn't even open the Mac since they could not reproduce the screen problem I have.
Click to expand...

Looks fine, as far as pagein/pageouts go. It was a long shot.

Next, check processes in Activity Monitor (make sure it's set to "all"). Maybe the drive is indexing - Spotlight should show that sort of activity. Otherwise, you could possibly find some other process hogging CPU and/or disk resources.
 
Right now I now I have only an SSH access to my Mac. I have a VNC running but it looks like it crashed as well and even the "reboot" command fails. The top command show some processes that are "stucked".

Code: 
PID  COMMAND      %CPU TIME     #TH  #WQ  #POR #MRE RPRVT  RSHRD  RSIZE  VPRVT  VSIZE  PGRP PPID STATE    UID  FAULTS   COW   MSGSENT   MSGRECV   SYSBSD   SYSMACH
792  reboot       0.0  00:00.04 1    0    17   24   92K    252K   360K   9560K  2378M  792  788  stuck    0    648      89    284       122       938      205
778  reboot       0.0  00:00.08 1    0    18   24   92K    252K   360K   9560K  2378M  778  633  stuck    0    1526     104   324       133       1085     235
729- OSXvnc-serve 0.0  00:26.44 7    1    91   95   2200K  8536K  4528K  33M    890M   729  633  stuck    501  9821     201   314531    149989    23866    287439
676  repair_packa 0.0  00:02.75 2    1    28   127  92M    7920K  98M    114M   2483M  676  573  stuck    0    25267    107   304       88        156388   242
574  repair_packa 0.0  00:02.74 2    1    28   126  92M    7920K  98M    106M   2475M  574  573  stuck    0    25260    90    304       88        156386   242
559  reboot       0.0  00:00.05 1    0    18   24   92K    252K   360K   9560K  2378M  559  1    stuck    0    652      90    283       121       941      204
555  repair_packa 0.0  00:02.74 2    1    28   127  92M    7920K  98M    114M   2483M  555  1    stuck    0    25262    89    304       88        156389   242
544  repair_packa 0.0  00:02.65 2    1    28   126  92M    7920K  98M    106M   2475M  544  1    stuck    0    25266    92    304       88        156386   242
539  repair_packa 0.0  00:02.74 2    1    28   126  92M    7920K  98M    106M   2475M  539  1    stuck    0    25268    92    304       88        156386   242
529  repair_packa 0.0  00:02.74 2    1    28   126  92M    7920K  98M    106M   2475M  529  1    stuck    0    25264    93    304       88        156386   242
512  repair_packa 0.0  00:02.65 2    1    28   126  92M    7920K  98M    106M   2475M  512  1    stuck    0    25260    91    304       88        156386   242
507  repair_packa 0.0  00:02.74 2    1    28   127  92M    7920K  98M    107M   2476M  507  1    stuck    0    25264    90    304       88        156388   242
419  repair_packa 0.0  00:02.95 2    1    28   127  92M    7920K  98M    114M   2483M  419  1    stuck    0    25262    92    304       88        156389   242
269  repair_packa 0.0  00:06.49 2    1    28   127  92M    7920K  98M    114M   2483M  269  1    stuck    0    25304    91    304       88        156388   242

It looks like some repair permissions processes are still running.

I tried to kill -9 all those processes but it has no effect :(
 
Ha so I managed to reboot it usign "reboot -q -n"

So after a clean boot, this is the output of top, sorted by cpu usage
Code: 
Processes: 62 total, 2 running, 60 sleeping, 227 threads                                                                                                                                             14:21:16
Load Avg: 0.04, 0.08, 0.04  CPU usage: 0.44% user, 1.9% sys, 98.45% idle   SharedLibs: 6988K resident, 10M data, 0B linkedit. MemRegions: 5491 total, 131M resident, 14M private, 98M shared.
PhysMem: 756M wired, 235M active, 92M inactive, 1083M used, 3013M free. VM: 129G vsize, 1041M framework vsize, 28032(2) pageins, 0(0) pageouts. Networks: packets: 3172/671K in, 3151/536K out.
Disks: 32417/1103M read, 6625/83M written.

PID  COMMAND          %CPU TIME     #TH  #WQ  #POR #MRE RPRVT  RSHRD  RSIZE  VPRVT  VSIZE  PGRP PPID STATE    UID  FAULTS COW   MSGSENT MSGRECV SYSBSD  SYSMACH CSW    PAGEI USER
201  SystemUIServer   1.0  00:03.71 3    1    247  216  5816K+ 10M-   13M+   34M+   2697M  201  196  sleeping 501  7052+  384   37861+  19271+  32966+  30301+  12836+ 1233  jan
128- iStatLocalDaemon 0.6  00:01.81 3    1    39   48   524K   3996K  2064K  28M    610M   128  1    sleeping 0    19136+ 159   369906+ 186177+ 16262+  208662+ 2761+  586   root
0-   kernel_task      0.5  00:07.02 62/3 0    2    774  23M    0B     154M   121M   2046M  0    0    running  0    10922  0     860197+ 853801+ 0       0       98371+ 0     root
263  top              0.2  00:00.13 1/1  0    24   44   1776K+ 264K   2348K+ 18M    2379M  263  254  running  0    2981+  55    57637+  28803+  990+    29099+  36+    0     root
110  mds              0.2  00:03.26 5    4    97+  276+ 34M-   4060K  26M-   155M-  2547M+ 110  1    sleeping 0    26345+ 132   14696+  7861+   33523+  8526+   7020+  3901+ root
142  WindowServer     0.1  00:06.62 4    1    186  408  -6M+   22M+   25M+   1004M+ 2977M  142  1    sleeping 88   12294+ 222   16756+  7267+   5348+   13839+  4560+  1559  _windowserver
127- iStatServer      0.0  00:00.18 3    1    72   73   812K   7140K  2780K  30M    616M   127  1    sleeping 0    3000+  188   4151+   2154+   1727+   3380+   754+   895   root
22   securityd        0.0  00:00.13 3    0    102- 39-  1620K- 4084K  2880K- 27M-   2402M- 22   1    sleeping 0    1663+  173   1530+   610+    1795+   4305+   760+   327   root
229  GrowlHelperApp   0.0  00:00.16 3    1    96   113  7712K  7184K  15M    23M    2688M  229  196  sleeping 501  6432   203   3315+   1556+   5071    2472+   755+   226   jan
227  locationd        0.0  00:00.14 10   1    97   78   2192K  6420K  4088K  44M    2422M  227  1    sleeping 205  1394   102   1343+   535+    3671+   1545+   1205+  230   _locationd
102  ntpd             0.0  00:00.03 1    0    23   24   544K   244K   1244K  17M    2378M  102  1    sleeping 0    761+   162   402     170     2822+   281     411+   73    root
253  sshd             0.0  00:00.05 1    0    11   69   276K   3528K  728K   416K   2393M  250  250  sleeping 501  239    95    36      15      2426+   29      222+   8     jan
115  fseventsd        0.0  00:00.03 11   1    91   63   1084K+ 244K   1588K+ 33M    2394M  115  1    sleeping 0    698+   57    817     354     1112+   1129+   752+   4     root
222  uc               0.0  00:00.05 5    2    76   64   1896K  6240K  5800K+ 31M    2407M  222  196  sleeping 501  1751+  120   840+    359+    1494+   751+    384+   69    jan
245  mdworker         0.0  00:00.09 3    1    64   61   1536K  8348K  3576K  23M    2409M  245  1    sleeping 89   1970+  130   1005+   381+    4640+   740+    360+   0     _spotlight
244  mdworker         0.0  00:00.37 3    1    50   71   2644K  8152K  8604K  24M    2410M  244  1    sleeping 501  3719+  168   1707+   647+    7427+   1152+   971+   460   jan
212  quicklookd       0.0  00:00.11 6    2    83   71   3408K  6208K  5820K  542M   2918M  212  196  sleeping 501  2098   147   2784    1392    4985+   2199    1377+  161   jan
12   notifyd          0.0  00:00.06 2    0    109  28   404K   244K   688K   19M    2387M  12   1    sleeping 0    1550+  42    11355+  5591+   179     10906+  1279+  3     root
13   diskarbitrationd 0.0  00:00.06 2    1    101- 41-  772K-  248K   1480K- 21M-   2389M- 13   1    sleeping 0    1253   387   2628+   1304+   785+    1582+   239+   41    root
10   kextd            0.0  00:01.31 2    1    43-  62-  1020K- 244K   2416K- 14M-   2391M- 10   1    sleeping 0    4723   118   903+    416+    5256+   598+    320+   388   root
16   distnoted        0.0  00:00.05 2    1    58-  38-  708K-  240K   1180K- 29M-   2389M- 16   1    sleeping 1    459    60    5785+   3242+   718+    3958+   994+   6     daemon
11   DirectoryService 0.0  00:02.80 4    2    71-  57-  2396K- 248K   4456K- 15M-   2394M- 11   1    sleeping 0    11772  118   13202+  6928+   194650+ 11335+  7318+  622   root
15   configd          0.0  00:01.68 5    1    225- 87-  864K-  3992K  2940K- 14M-   2405M- 15   1    sleeping 0    11319  97    74456+  34611+  7528+   44417+  8446+  303   root
17   mDNSResponder    0.0  00:00.09 3    1    48   56   896K   280K   1788K  41M    2401M  17   1    sleeping 65   789    89    1137+   434+    3976    787+    786+   87    _mdnsresponder
254  bash             0.0  00:00.02 1    0    17   25   300K   244K   980K   17M    2378M  254  253  sleeping 501  760    258   122     52      1646    93      104    51    jan
250  sshd             0.0  00:00.08 2    1    37   69   496K   3528K  4724K  640K   2393M  250  1    sleeping 0    2209   319   568     236     2029    383     110    182   root
235  ocspd            0.0  00:00.01 1    0    25   28   536K   304K   1240K  17M    2378M  235  1    sleeping 0    450    57    140     63      188     600     30     37    root
234  System Events    0.0  00:00.23 2    1    71   106  2328K  7316K  9212K  22M    2679M  234  196  sleeping 501  4268   248   2142    872     8651    1376    548    171   jan
231- LCCDaemon        0.0  00:00.18 2    1    98   123  2080K  8052K  5016K  178M   1037M  231  196  sleeping 501  3750   670   3291    1554    3324    2238    3324   907   jan
230  iTunesHelper     0.0  00:00.03 3    1    40   73   1088K  5208K  3164K  22M    2406M  230  196  sleeping 501  1027   147   886     395     708     484     108    80    jan
228  CCacheServer     0.0  00:00.01 2    2    35   50   584K   244K   1592K  31M    2391M  228  196  sleeping 501  585    78    356     162     311     248     116    1     jan
224  iStatLocal       0.0  00:00.03 2    1    52   69   1552K  6268K  4928K  40M    2672M  224  196  sleeping 501  1533   135   616     278     789     408     151    10    jan
221  AirPort Base Sta 0.0  00:00.01 4    1    50   52   632K   244K   1676K  22M    2390M  221  196  sleeping 501  606    77    288     133     473     199     68     1     jan
215  UserEventAgent   0.0  00:00.19 3    1    171  114  2332K  2560K  5752K  33M    2660M  215  196  sleeping 501  5543   136   4667    2176    1547    2461    312    13    jan
210  fontd            0.0  00:00.14 2    1    74   106  3292K  6208K  4280K  62M    2438M  210  196  sleeping 501  2164   225   2626    1376    9066    4542    2437   4     jan
204  pboard           0.0  00:00.00 1    0    22   37   360K   248K   836K   18M    2379M  204  196  sleeping 501  352    59    160     73      124     131     34     1     jan
202  Finder           0.0  00:00.42 4    1    161  182  3432K+ 15M-   14M    18M+   2708M  202  196  sleeping 501  6690   299   9936    4588    7578    7851    2219   1660  jan
200  Dock             0.0  00:00.71 3    1    104  256  3768K  25M    20M    17M    2693M  200  196  sleeping 501  19153  359   4235    1572    9532    3289    2646   2010  jan
196  launchd          0.0  00:00.04 2    0    157  56   476K   468K   940K   38M    2399M  196  1    sleeping 501  1577   980   3382    1347    6041    2579    1071   0     jan
191  coreaudiod       0.0  00:00.04 2    1    118  64   796K   328K   1504K  30M    2391M  191  1    sleeping 202  1012   85    3264    1579    677     1783    244    89    _coreaudiod
184  cvmsComp_x86_64  0.0  00:00.17 1    0    18   34   1748K  244K   6328K  18M    2392M  184  182  sleeping 212  1853   130   214     102     206     153     70     1055  _cvmsroot
182  launchd          0.0  00:00.00 2    0    37   46   236K   428K   660K   30M    2399M  182  1    sleeping 212  377    122   404     174     480     269     69     0     _cvmsroot
181  cvmsServ         0.0  00:00.00 2    0    43   29   336K   248K   804K   19M    2381M  181  1    sleeping 0    475    79    283     132     222     197     31     0     root
179* privoxy          0.0  00:00.06 1    0    16   90   3344K  244K   3604K  68M    651M   179  1    sleeping 0    1176   284   72      35      1993    54      28     108   root
165- vmnet-bridge     0.0  00:00.00 2    1    26   60   336K   1128K  968K   21M    602M   164  1    sleeping 0    358    62    217     100     208     146     60     6     root
162- vmnet-dhcpd      0.0  00:00.00 1    0    10   46   324K   1744K  288K   18M    592M   162  1    sleeping 0    83     11    28      11      25      25      15     0     root
157- vmnet-netifup    0.0  00:00.00 1    0    8    45   228K   1660K  188K   10M    591M   157  1    sleeping 0    53     14    18      9       9       16      1      0     root
 
I had the same exact or at least similar problem but only on my new mbp running Sl. I've had no problems with my mba or imac running SL

Initially, took to Apple where they replaced the HHD, but that didn't fix the issue. So if it comes down to it and you decide to send/take it in, not that you can really tell them what to do, since they have their own protocols to follow after any diagnostics test...anyway

After I got it back, I was still getting the spinning wheel. Here's what I found, whenever I got the spinning wheel, I would open Activity Monitor > CPU and I noticed that I was using a lot of cpu on nothing really. I typically saw the spinning wheel when I was just browsing the internet. But I saw this one, odd process name (which unfortunately I cannot remember, sorry) that was using a considerable amount of cpu. To help narrow it down, it was a process under the computer's name i.e. my computer's name is my name, in other words it wasn't root or a computer run process.

Whatever it was I was using it somewhere. In any event, I went down the list of things that I didn't know what it was and killed them. I did this until I found the process that stopped using so much cpu. Once I narrrowed it down to that specific process, I did a "finder" on it and deleted all of the files associated with it. Then I also deleted all of my cache files.

Probably not the "do this, do this, then do this" answer you are looking for, but this was what I did, and have had no problems since.

[EDIT] I should also note that this took me some time, as I had to kill one process at a time, then mess around to see if I could duplicate the problem. Probably took me about a half hour or so. But it was definitely worth it. That was very frustrating!

Good luck

-side note, what would "pageins: and "pageouts" have to do with anything?
 
So now I booted from SL install CD and run the repair permission from there. It went through, I rebooted again to my normal SL and run repair permissions again and this time it worked also. There were suspicious messages.

Now I wait and see (and hope) that the OS won't hang all the time ...


EDIT: :mad::mad::mad: Damn it hanged again. What the **** did they do with my mac.
 
The spinning wheel can mean numerous things, but both my iMac (early 08) and Macbook (late 07) suffered from it after 'upgrade' installations of Snow Leopard.

I gave up after a couple of weeks and did fresh installs on both, and they now both run beautifully.

Worth a try, even if it is a bit of work.
 
jdavtz said:
The spinning wheel can mean numerous things, but both my iMac (early 08) and Macbook (late 07) suffered from it after 'upgrade' installations of Snow Leopard.

I gave up after a couple of weeks and did fresh installs on both, and they now both run beautifully.

Worth a try, even if it is a bit of work.
Click to expand...

I had a clean install of SL which was running perfectly fine untill I got the MBP back from AppleCare.
 
Wirelessly posted (Mozilla/5.0 (iPhone; U; CPU iPhone OS 3_0_1 like Mac OS X; en-us) AppleWebKit/528.18 (KHTML, like Gecko) Version/4.0 Mobile/7A400 Safari/528.16)

I gave up. I formatted the disk and I'm installing SL from scratch. Windows style.
 
So here we go again :mad::mad::mad:

One month after reinstalling it, SL started to crash again. It happens line 1 in 3 days.

I suspect Firefox this time. I had a look at the system.log and I see this:
Code: 
Nov 21 08:05:12 Jan /System/Library/CoreServices/CCacheServer.app/Contents/MacOS/CCacheServer[121]: No valid tickets, timing out
Nov 21 08:05:20 Jan firefox-bin[241]: *** __NSAutoreleaseNoPool(): Object 0x138bb920 of class NSCFString autoreleased with no pool in place - just leaking
Nov 21 08:05:20 Jan firefox-bin[241]: *** __NSAutoreleaseNoPool(): Object 0x1509fe0 of class NSPathStore2 autoreleased with no pool in place - just leaking
Nov 21 08:05:20 Jan firefox-bin[241]: *** __NSAutoreleaseNoPool(): Object 0x150f600 of class NSPathStore2 autoreleased with no pool in place - just leaking
Nov 21 08:05:20 Jan firefox-bin[241]: *** __NSAutoreleaseNoPool(): Object 0x138bf390 of class NSPathStore2 autoreleased with no pool in place - just leaking
Nov 21 08:05:20 Jan firefox-bin[241]: *** __NSAutoreleaseNoPool(): Object 0x138bbe10 of class NSPathStore2 autoreleased with no pool in place - just leaking
Nov 21 08:05:20 Jan firefox-bin[241]: *** __NSAutoreleaseNoPool(): Object 0x138bbf10 of class NSPathStore2 autoreleased with no pool in place - just leaking
Nov 21 08:05:20 Jan firefox-bin[241]: *** __NSAutoreleaseNoPool(): Object 0x138bef40 of class NSPathStore2 autoreleased with no pool in place - just leaking
Nov 21 08:05:20 Jan firefox-bin[241]: *** __NSAutoreleaseNoPool(): Object 0x150f6d0 of class NSPathStore2 autoreleased with no pool in place - just leaking
Nov 21 08:05:20 Jan firefox-bin[241]: *** __NSAutoreleaseNoPool(): Object 0x138bc010 of class NSPathStore2 autoreleased with no pool in place - just leaking
Nov 21 08:05:20 Jan firefox-bin[241]: *** __NSAutoreleaseNoPool(): Object 0x150f790 of class NSPathStore2 autoreleased with no pool in place - just leaking
Nov 21 08:05:20 Jan firefox-bin[241]: *** __NSAutoreleaseNoPool(): Object 0x150fa00 of class NSPathStore2 autoreleased with no pool in place - just leaking
Nov 21 08:05:20 Jan firefox-bin[241]: *** __NSAutoreleaseNoPool(): Object 0x150d4e0 of class __NSCFDate autoreleased with no pool in place - just leaking
Nov 21 08:05:20 Jan firefox-bin[241]: *** __NSAutoreleaseNoPool(): Object 0x138bee10 of class NSCFString autoreleased with no pool in place - just leaking
Nov 21 08:05:20 Jan firefox-bin[241]: *** __NSAutoreleaseNoPool(): Object 0x138bf010 of class NSCFString autoreleased with no pool in place - just leaking
Nov 21 08:05:20 Jan firefox-bin[241]: *** __NSAutoreleaseNoPool(): Object 0x138bef00 of class NSCFSet autoreleased with no pool in place - just leaking
Nov 21 08:05:20 Jan firefox-bin[241]: *** __NSAutoreleaseNoPool(): Object 0x150d6f0 of class __NSCFDate autoreleased with no pool in place - just leaking
Nov 21 08:05:20 Jan firefox-bin[241]: *** __NSAutoreleaseNoPool(): Object 0x150ff60 of class NSCFTimer autoreleased with no pool in place - just leaking
Nov 21 08:05:20 Jan firefox-bin[241]: *** __NSAutoreleaseNoPool(): Object 0x138bf0e0 of class __NSCFDate autoreleased with no pool in place - just leaking
Nov 21 08:05:20 Jan firefox-bin[241]: Can't open input server /Library/InputManagers/MultiClutchInputManager.bundle

It looks like memory leak ?
 
Hmm I dont think it's because of Firefox. There are jsut some processes STUCK. Check the state column in the top output.

Code: 
PID   COMMAND      %CPU TIME     #TH  #WQ  #POR #MREG RPRVT  RSHRD  RSIZE  VPRVT  VSIZE  PGRP PPID STATE    UID
2329  bsdtar       0.0  00:00.01 1    0    14   27    320K   240K   732K   9572K  2378M  2329 1    stuck    501
1364- GoogleSoftwa 0.0  00:03.54 6    2    101  129   2216K  6412K  6200K  32M    892M   1364 89   stuck    501
1354  docsetinstal 0.0  00:05.56 3    1    60   200   133M   3108K  137M   171M   2546M  1354 1    stuck    59
95    Finder       0.0  00:08.93 6    2    186  213   8444K  44M    26M    32M    2759M  95   89   stuck    501
45    fseventsd    0.0  00:03.93 19   1    140  79    2676K  244K   3220K  37M    2398M  45   1    stuck    0
40    mds          0.0  00:53.41 4    3    95-  168-  18M-   6680K  32M-   158M-  2546M- 40   1    stuck    0
1     launchd      0.0  00:04.21 3    0    124  56    736K   460K   1168K  38M    2399M  1    0    stuck    0
 
I may be wrong, but to me it sounds like clean install time.

Not sure whether you upgraded from Leopard to SL or did a clean install, certainly a fresh installation of SL should clear any problems.

The upgrade on my MacBook sucked. Clean install and now it's running smooth as a babies bottom.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back