Blocco del leone di montagna

Il mio Mountain Lion continua a congelarsi da poche settimane, oggi si blocca / si è schiantato già un paio di volte.

Ecco il registro prima del grande blocco (file /var/log/system.log):

SIMBL Enabler for Sandboxed Apps[3334]: Will terminate until reinvoked again by launchd.
com.apple.launchd.peruser.501[265] (com.apple.pbs[3243]): Exited: Killed: 9
kernel[0]: memorystatus_thread: idle exiting pid 3243 [pbs]
com.apple.launchd[1] (com.apple.iCloudHelper[3241]): Exited: Killed: 9
kernel[0]: memorystatus_thread: idle exiting pid 3241 [com.apple.iCloud]
com.apple.launchd[1] (com.apple.xpcd.F5010000-0000-0000-0000-000000000000[3238]): Exited: Killed: 9
kernel[0]: memorystatus_thread: idle exiting pid 3238 [xpcd]
com.apple.launchd[1] (com.apple.sleepservicesd[3237]): Exited: Killed: 9
kernel[0]: memorystatus_thread: idle exiting pid 3237 [SleepServicesD]
com.apple.launchd.peruser.501[265] (com.apple.CalendarAgent[3188]): Exited: Killed: 9
kernel[0]: memorystatus_thread: idle exiting pid 3188 [CalendarAgent]
kernel[0]: (default pager): [KERNEL]: ps_select_segment - send HI_WAT_ALERT
kernel[0]: macx_swapon SUCCESS
com.apple.launchd[1] (com.apple.sleepservicesd[3362]): Exited: Killed: 9
kernel[0]: memorystatus_thread: idle exiting pid 3362 [SleepServicesD]
SubmitDiagInfo[3240]: Launched to submit Diagnostics and Usage
com.apple.launchd[1] (com.apple.cfprefsd.xpc.daemon[3235]): Exited: Killed: 9
kernel[0]: memorystatus_thread: idle exiting pid 3235 [cfprefsd]
WindowServer[222]: reenable_update_for_connection: UI updates were finally reenabled by application "Activity Monitor" after 125.95 seconds (server forcibly re-enabled them after 1.00 seconds)
com.apple.launchd[1] (com.apple.sleepservicesd[3364]): Exited: Killed: 9
kernel[0]: memorystatus_thread: idle exiting pid 3364 [SleepServicesD]
coreaudiod[249]: Disabled automatic stack shots because audio IO is active
coreaudiod[249]: Enabled automatic stack shots because audio IO is inactive
com.apple.launchd.peruser.501[265] (com.apple.pbs[3369]): Exited: Killed: 9
kernel[0]: memorystatus_thread: idle exiting pid 3369 [pbs]
com.apple.launchd[1] (com.apple.sleepservicesd[3368]): Exited: Killed: 9
kernel[0]: memorystatus_thread: idle exiting pid 3368 [SleepServicesD]
com.apple.launchd[1] (com.apple.cfprefsd.xpc.daemon[3366]): Exited: Killed: 9
com.apple.launchd.peruser.501[265] (com.apple.cfprefsd.xpc.agent[3225]): Exited: Killed: 9
kernel[0]: memorystatus_thread: idle exiting pid 3366 [cfprefsd]
kernel[0]: memorystatus_thread: idle exiting pid 3225 [cfprefsd]
com.apple.launchd[1] (com.apple.sleepservicesd[3387]): Exited: Killed: 9
kernel[0]: memorystatus_thread: idle exiting pid 3387 [SleepServicesD]
com.apple.launchd[1] (com.apple.locationd[3191]): Exited with code: 1
com.apple.launchd[1] (com.apple.sleepservicesd[3388]): Exited: Killed: 9
kernel[0]: memorystatus_thread: idle exiting pid 3388 [SleepServicesD]
locationd[3405]: Incorrect NSStringEncoding value 0x8000100 detected. Assuming NSASCIIStringEncoding. Will stop this compatiblity mapping behavior in the near future.
locationd[3405]: NOTICE,Location icon should now be in state 0
locationd[3405]: locationd was started after an unclean shutdown
com.apple.launchd[1] (com.apple.sleepservicesd[3406]): Exited: Killed: 9
kernel[0]: memorystatus_thread: idle exiting pid 3406 [SleepServicesD]
com.apple.launchd[1] (com.apple.cfprefsd.xpc.daemon[3407]): Exited: Killed: 9
kernel[0]: memorystatus_thread: idle exiting pid 3407 [cfprefsd]
com.apple.launchd[1] (com.apple.sleepservicesd[3408]): Exited: Killed: 9
kernel[0]: memorystatus_thread: idle exiting pid 3408 [SleepServicesD]
com.apple.launchd[1] (com.apple.sleepservicesd[3412]): Exited: Killed: 9
kernel[0]: memorystatus_thread: idle exiting pid 3412 [SleepServicesD]
kernel[0]: (default pager): [KERNEL]: ps_select_segment - send HI_WAT_ALERT
kernel[0]: memorystatus_thread: idle exiting pid 3416 [SleepServicesD]
com.apple.launchd[1] (com.apple.sleepservicesd[3416]): Exited: Killed: 9
kernel[0]: macx_swapon SUCCESS
WindowServer[222]: CGXDisableUpdate: UI updates were forcibly disabled by application "Finder" for over 1.00 seconds. Server has re-enabled them.
WindowServer[222]: reenable_update_for_connection: UI updates were finally reenabled by application "Finder" after 11.80 seconds (server forcibly re-enabled them after 1.23 seconds)
kernel[0]: memorystatus_thread: idle exiting pid 3448 [SleepServicesD]
com.apple.launchd[1] (com.apple.sleepservicesd[3448]): Exited: Killed: 9
bootlog[0]: BOOT_TIME 1379512956 0
kernel[0]: Darwin Kernel Version 12.4.0: Wed May  1 17:57:12 PDT 2013; root:xnu-2050.24.15~1/RELEASE_X86_64

Sembra che la maggior parte dei processi vengano uccisi per motivi sconosciuti. Ciò accade anche dopo un nuovo riavvio e l'apertura di alcune schede del browser Web Chrome. Sulla base dei registri, sembra che MACX Swap abbia iniziato a essere utilizzato, nonostante la memoria da 4 GB. Ho verificato l'utilizzo elevato in Activity Monitor e i più alti sono stati kernel e mds con un utilizzo di circa 800 MB. Vi è abbondanza di spazio su HDD (SDD).

Questo problema è ampiamente sperimentato, quindi per favore non sottovalutarlo.

Relazionato:

Mountain Lion Screen Freeze (oltre 177 risposte)

MacBook Pro Freezing

Indicare le soluzioni e i test che possono essere eseguiti a livello di software, ecc. Cosa si può fare per tenere traccia dei problemi più comuni del genere.

suggerimenti:

• Esegui il kill -CONT -1comando per sbloccare tutte le potenziali applicazioni pauzed / frozen.

• Esegui Mac in modalità di ripristino (mantieni premuto ⌘ cmd+ Rall'avvio), quindi prova a riparare il disco e ripara le autorizzazioni del disco utilizzando Utility Disco.

• Come suggerito nel thread Mountain Lion Screen Freeze , prova il software OnyX che consente e verifica il disco di avvio e la struttura dei suoi file di sistema, ecc.

• Esegui dmesg e verifica la presenza /var/log/system.logdi errori più dettagliati.

• Esegui l'app Console per controllare i registri degli arresti anomali, inclusi eventuali backtrace.

• Esegui newproc.do iofile.d trascina gli script per trovare qualcosa di sospetto (ad es. sudo newproc.d)

• Esegui test di memoria (ad es. Utilizzando l' app Rember )