Startup hang: grey screen, spinning wheel, then automatic reset to same
Brand new imac, installed 10.5, updated to 10.5.1, ported over a few dozen applications, utilities and preferences, plus 20,000 files from G4 running 10.3.1, using the "migration assistant."
Took the obviously useless/ redundant apps and utilities out...plus some light, but possibly ill-advised pruning of what seemed like way outdated library items
Killed the automatically generated new user in favor of the migration-assistant ported over and updated G4 identity...(or was this where I went wrong?)
did some more house cleaning, including installing new versions of several pieces of software, including sheepshaver, and (last thing done) parallels with windows XP.
Everything working hunky dory...woo hoo, fast new computer ready for biz mon...but no;
After shutdown, it won't start up; hangs on grey screen with spinning clock, then resets...
Restarts fine from install disk, did disk utility/repair disk, no problems found, same issue on startup
My plan is to
1) repair permissions, try starting up
2) re-install system, with old system archieved, try starting up again
Any insights most welcome...
UPDATE:
First, forgot to mention that I'd globally changed permissions to read/write all around on the whole drive.
Second, I'll be darned if the Disk Utility/ Repair Permissions thing didn't unhang it...so much for the doubters I saw on some other forum post who said this is mere voodoo...
After a few hours of permissions repair, on a successful restart, it identified a bunch of startup item issues, which I fixed or deleted, and now all but parallels works. We'll see what happens after I reinstall parallels...
Similar Messages
-
MBP won't boot - Grey Apple Screen, Spinning Wheel, then Shut Down
Help please
For no apparent reason, my otherwise well-working MBP (2007 model) simply won't log in to OSX (leopard). I try to boot it up, and I get the grey screen with the Apple logo, the spinning progress wheel, and then after about 4 minutes, it just powers off.
Thoughts?adammabry wrote:
I ran verify because the option to run repair was not available.
And just to make sure, you booted from the install disc? (Repair Disk is never available when booted on the boot volume of the HD.)
Here's a follow up... This mac wasn't doing it's airport backups properly,
I'm not quite sure what that means, maybe Time Machine? Time Capsule?
so I don't have a recent back up of the files. Would you suggest just sending the computer to a data recovery service?
Very expensive. Try FireWire Target Disk Mode first. If that doesn't work, I'd remove the HD, install it in an external enclosure (as low as $15) and see if it will boot the MBP or the data is accessible from another Mac.
Do you think I can just pop a new HD in it and it'll work fine under a full reinstall?
Doing my previous suggestions first may help to answer that. If there's absolutely nothing wrong with the HD, then that isn't the issue. If there is something wrong with it, likely a new HD is the fix. -
Mac mini shut down on its own. Could not restart, chime, grey screen and spinning wheel. Unplugged everything but monitor, still only chime, grey screen and spinning wheel. Started in safe boot, shut Down, will not restart.
This happened a couple of months ago, unplugged everything and it restarted, now that won't work.Hi BDAqua,
I just did the repair as you suggested. T ran the disc repair, and twice it cam back, the volume macintosh seems ti be okay, I also ran the verify and permissions repair, both came back okay.
I was actually hoping that they would find something, so they could repair. I shut the computer down, and restated with out holding a key, and I started up great. I'm baffled. I have moved 20 GB to an external hard drive, as I only had 10% open space.
I have Tech Tool 6, would you recommend to run a repair check on that, or just leave well enough alone.
I agree with you on the new Mac's, I have problems with no disc for back up, until they realize their mistake I will stay with Snow a Leopard. This is the first problem I have experienced, so I can't complain. Their last programs are not as perfected as under Steve, prior to his handling over the reins, hope this is not going to be the future we can expect from Apple.
I will wait to here back as to your suggestion regarding the Tech Tool check
Thanks for all your help.
Gratefully,
Cheri -
Imac stuck at grey screen ( spinning wheel) i accidentally disconnected my keyboard, any help
i've tried everything. but i try going to safe mode but my keyboard is disconnected so i cant do much, ANY HELP??
Do you have access to a USB keyboard?
Startup - Gray, Blue or White screen at boot, w/spinner/progress bar
Startup Issues - Resolve
Startup Issues - Resolve (2) -
New Mac froze overnight. Tried to power up just grey screen spinning.
New 21.5 iMac froze over night. Now just grey screen spinning wheel. No safe mode. Able to boot up in recovery disc once. Fixed permissions ? Restarted to no resolve. Tried again but mouse not working past mouse start up click freeze... Have also looked and found a problem boot cache control : unable to open..
Any ideas any one this Mac is 3 weeks oldI'd return it myself, but...
Bootup holding CMD+r, or the Option/alt key to boot from the Restore partition & use Disk Utility from there to Repair the Disk, then Repair Permissions.
If that doesn't help Reinstall the OS. -
System startup Problem grey screen is going regularly and automatically shutdown
Hi
kindly resolve us this problem urgently
error msg. :- System startup Problem grey screen is going regularly and automatically shutdown
thanks
Dhaval OzaUse RECOVERY MODE.
Boot from another drive with a copy of OS X too is always good.
A Safe Boot at a minimum. -
Imac intel won't restart, I get gray screen and spinning wheel then shut off
My imac intel only restart after running disk utility, otherwise I get a gray screen with apple logo and spinning wheel then after about 2min it shuts off. this all started after a power outage. I have tried everything that I have read online to fix this, it seems doing a clean install is last resort. Does anyone have any other options for me?
nessman wrote:
I have tried disconnecting the periperals, restarting in "safe boot", resetting the pram and I tried starting up in single user mode. It will only start up if I start up from the original gray 10.4 start up disk and run "repair disk"....I get errors including "The underlying task reported failure on exit". I then eject the disk and restart and it works fine but if I have to shut down or restart for any reason it's back to the gray screen.
Your system profile confirms you are using OS 10.5.8. Boot up from your OS 10.5.x install dvd. Use the "repair disk" setting. If you get the same error, then run Apple Hardware Test from your original system dvd. -
On start up I get grey screen with wheel turning but it goes no further
On start up I get grey screen with wheel turning but it goes no further
Take each of these steps that you haven't already tried. Stop when the problem is resolved.
Step 1
The first step in dealing with a startup failure is to secure the data. If you want to preserve the contents of the startup drive, and you don't already have at least one current backup, you must try to back up now, before you do anything else. It may or may not be possible. If you don't care about the data that has changed since the last backup, you can skip this step.
There are several ways to back up a Mac that is unable to start. You need an external hard drive to hold the backup data.
a. Start up from the Recovery partition, or from a local Time Machine backup volume (option key at startup.) When the OS X Utilities screen appears, launch Disk Utility and follow the instructions in this support article, under “Instructions for backing up to an external hard disk via Disk Utility.” The article refers to starting up from a DVD, but the procedure in Recovery mode is the same. You don't need a DVD if you're running OS X 10.7 or later.
b. If Step 1a fails because of disk errors, and no other Mac is available, then you may be able to salvage some of your files by copying them in the Finder. If you already have an external drive with OS X installed, boot from it. Otherwise, if you have Internet access, follow the instructions on this page to prepare the external drive and install OS X on it. You'll use the Recovery installer, rather than downloading it from the App Store.
c. If you have access to a working Mac, and both it and the non-working Mac have FireWire or Thunderbolt ports, start the non-working Mac in target disk mode. Use the working Mac to copy the data to another drive. This technique won't work with USB, Ethernet, Wi-Fi, or Bluetooth.
d. If the internal drive of the non-working Mac is user-replaceable, remove it and mount it in an external enclosure or drive dock. Use another Mac to copy the data.
Step 2
If the startup process stops at a blank gray screen with no Apple logo or spinning "daisy wheel," then the startup volume may be full. If you had previously seen warnings of low disk space, this is almost certainly the case. You might be able to start up in safe mode even though you can't start up normally. Otherwise, start up from an external drive, or else use the technique in Step 1b, 1c, or 1d to mount the internal drive and delete some files. According to Apple documentation, you need at least 9 GB of available space on the startup volume (as shown in the Finder Info window) for normal operation.
Step 3
Sometimes a startup failure can be resolved by resetting the NVRAM.
Step 4
If you use a wireless keyboard, trackpad, or mouse, replace or recharge the batteries. The battery level shown in the Bluetooth menu item may not be accurate.
Step 5
If there's a built-in optical drive, a disc may be stuck in it. Follow these instructions to eject it.
Step 6
Press and hold the power button until the power shuts off. Disconnect all wired peripherals except those needed to start up, and remove all aftermarket expansion cards. Use a different keyboard and/or mouse, if those devices are wired. If you can start up now, one of the devices you disconnected, or a combination of them, is causing the problem. Finding out which one is a process of elimination.
Step 7
If you've started from an external storage device, make sure that the internal startup volume is selected in the Startup Disk pane of System Preferences.
Start up in safe mode. Note: If FileVault is enabled, or if a firmware password is set, or if the startup volume is a Fusion Drive or a software RAID, you can’t do this. Post for further instructions.
Safe mode is much slower to start and run than normal, and some things won’t work at all, including wireless networking on certain Macs.
The login screen appears even if you usually log in automatically. You must know the login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
When you start up in safe mode, it's normal to see a dark gray progress bar on a light gray background. If the progress bar gets stuck for more than a few minutes, or if the system shuts down automatically while the progress bar is displayed, the startup volume is corrupt and the drive is probably malfunctioning. In that case, go to Step 10. If you ever have another problem with the drive, replace it immediately.
If you can start and log in in safe mode, empty the Trash, and then open the Finder Info window on the startup volume ("Macintosh HD," unless you gave it a different name.) Check that you have at least 9 GB of available space, as shown in the window. If you don't, copy as many files as necessary to another volume (not another folder on the same volume) and delete the originals. Deletion isn't complete until you empty the Trash again. Do this until the available space is more than 9 GB. Then restart as usual (i.e., not in safe mode.)
If the startup process hangs again, the problem is likely caused by a third-party system modification that you installed. Post for further instructions.
Step 8
Launch Disk Utility in Recovery mode (see Step 1.) Select the startup volume, then run Repair Disk. If any problems are found, repeat until clear. If Disk Utility reports that the volume can't be repaired, the drive has malfunctioned and should be replaced. You might choose to tolerate one such malfunction in the life of the drive. In that case, erase the volume and restore from a backup. If the same thing ever happens again, replace the drive immediately.
This is one of the rare situations in which you should also run Repair Permissions, ignoring the false warnings it may produce. Look for the line "Permissions repair complete" at the end of the output. Then restart as usual.
Step 9
If the startup device is an aftermarket SSD, it may need a firmware update and/or a forced "garbage collection." Instructions for doing this with a Crucial-branded SSD were posted here. Some of those instructions may apply to other brands of SSD, but you should check with the vendor's tech support.
Step 10
Reinstall the OS. If the Mac was upgraded from an older version of OS X, you’ll need the Apple ID and password you used to upgrade.
Step 11
Do as in Step 9, but this time erase the startup volume in Disk Utility before installing. The system should automatically restart into the Setup Assistant. Follow the prompts to transfer the data from a Time Machine or other backup.
Step 12
This step applies only to models that have a logic-board ("PRAM") battery: all Mac Pro's and some others (not current models.) Both desktop and portable Macs used to have such a battery. The logic-board battery, if there is one, is separate from the main battery of a portable. A dead logic-board battery can cause a startup failure. Typically the failure will be preceded by loss of the settings for the startup disk and system clock. See the user manual for replacement instructions. You may have to take the machine to a service provider to have the battery replaced.
Step 13
If you get this far, you're probably dealing with a hardware fault. Make a "Genius" appointment at an Apple Store, or go to another authorized service provider. -
My imac 10.6.8 hangs on the spinning wheel after installing Samsung Kies (KiesMac_2-0-0-13023_10_1).
I was able to restart ok after installation; I even moved some files from my
Galaxy 3 to the imac.
But on the next (and all subsequent) restart attempts, it hangs on the spinning wheel.
How to fix? Thanx in advance.Mac OS X: Gray screen appears during startup
-
Logi 9.1.7 still hanging and showing spinning wheel.... on os x lion...
Hi.
i am still having trouble with logic 9.1.7 and osx lion.
sometimes the program works fine with now hanging wheel, but most of the time the program will play, i can edit then for a few seconds it just hangs on the spinning wheel, continues play back and then becomes responsive again, this happens through out the program most of the time. This is most frustrating and damaging my work flow, so i want a solution. I've done the monitor activity, cancelled all login items, have enough ram and disk space on all drives. i have even taken a log of the process when it hangs via activity monitor.
Sampling process 588 for 3 seconds with 1 millisecond of run time between samples
Sampling completed, processing symbols...
Analysis of sampling Logic Pro (pid 588) every 1 millisecond
Process: Logic Pro [588]
Path: /Applications/Logic Pro.app/Contents/MacOS/Logic Pro
Load Address: 0x1000
Identifier: com.apple.logic.pro
Version: 9.1.7 (1700.57)
Build Info: Logic-17005700~1
Code Type: X86 (Native)
Parent Process: launchd [492]
Date/Time: 2012-06-21 11:15:29.398 +0100
OS Version: Mac OS X 10.7.4 (11E53)
Report Version: 7
Call graph:
1599 Thread_71503: Main Thread DispatchQueue_<multiple>
+ 1586 DummyConnection::DummyConnection() (in Logic Pro) + 193 [0x2b1c5]
+ ! 1586 NSProApplicationMain (in ProKit) + 439 [0xfcd42b]
+ ! 1575 -[NSApplication run] (in AppKit) + 911 [0x90021cb1]
+ ! : 1575 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] (in AppKit) + 113 [0x90025942]
+ ! : 1575 _DPSNextEvent (in AppKit) + 678 [0x900260d8]
+ ! : 1575 BlockUntilNextEventMatchingListInMode (in HIToolbox) + 88 [0x917538fa]
+ ! : 1575 ReceiveNextEventCommon (in HIToolbox) + 168 [0x917539b6]
+ ! : 1575 RunCurrentEventLoopInMode (in HIToolbox) + 318 [0x9174c723]
+ ! : 1575 CFRunLoopRunInMode (in CoreFoundation) + 120 [0x95686088]
+ ! : 1575 CFRunLoopRunSpecific (in CoreFoundation) + 332 [0x956861dc]
+ ! : 1492 __CFRunLoopRun (in CoreFoundation) + 1888 [0x95686cd0]
+ ! : | 1491 __CFRunLoopDoTimer (in CoreFoundation) + 743 [0x956a7c37]
+ ! : | + 1491 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ (in CoreFoundation) + 22 [0x956a82a6]
+ ! : | + 1490 __NSFireTimer (in Foundation) + 166 [0x90b0fbab]
+ ! : | + ! 1489 std::ostream& TraceOutContainer<CEvs>(std::ostream&, CEvs, char const*, int) (in Logic Pro) + 6131687 [0x614a57]
+ ! : | + ! : 1489 std::ostream& TraceOutContainer<CEvs>(std::ostream&, CEvs, char const*, int) (in Logic Pro) + 1639067 [0x1cbd0b]
+ ! : | + ! : 1489 std::ostream& TraceOutContainer<CEvs>(std::ostream&, CEvs, char const*, int) (in Logic Pro) + 6253110 [0x6324a6]
+ ! : | + ! : 1489 std::ostream& TraceOutContainer<CEvs>(std::ostream&, CEvs, char const*, int) (in Logic Pro) + 1625656 [0x1c88a8]
+ ! : | + ! : 1489 std::ostream& TraceOutContainer<CEvs>(std::ostream&, CEvs, char const*, int) (in Logic Pro) + 5443771 [0x56cb2b]
+ ! : | + ! : 1478 std::ostream& TraceOutContainer<CEvs>(std::ostream&, CEvs, char const*, int) (in Logic Pro) + 5519317 [0x57f245]
+ ! : | + ! : | 1478 std::ostream& TraceOutContainer<CEvs>(std::ostream&, CEvs, char const*, int) (in Logic Pro) + 4013142 [0x40f6c6]
+ ! : | + ! : | 1478 std::ostream& TraceOutContainer<CEvs>(std::ostream&, CEvs, char const*, int) (in Logic Pro) + 933013 [0x11f705]
+ ! : | + ! : | 1361 std::ostream& TraceOutContainer<CEvs>(std::ostream&, CEvs, char const*, int) (in Logic Pro) + 522563 [0xbb3b3]
+ ! : | + ! : | + 1361 std::ostream& TraceOutContainer<CEvs>(std::ostream&, CEvs, char const*, int) (in Logic Pro) + 484315 [0xb1e4b]
+ ! : | + ! : | + 1361 std::ostream& TraceOutContainer<CEvs>(std::ostream&, CEvs, char const*, int) (in Logic Pro) + 2411889 [0x2887e1]
+ ! : | + ! : | + 1326 std::ostream& TraceOutContainer<CEvs>(std::ostream&, CEvs, char const*, int) (in Logic Pro) + 2410189 [0x28813d]
+ ! : | + ! : | + ! 1326 ??? (in LionPanels) load address 0x2e9c000 + 0xd43f [0x2ea943f]
+ ! : | + ! : | + ! 1300 -[NSAlert runModal] (in AppKit) + 277 [0x902e7433]
+ ! : | + ! : | + ! : 1286 -[NSApplication runModalForWindow:] (in AppKit) + 258 [0x902f7024]
+ ! : | + ! : | + ! : | 1286 -[NSApplication _doModalLoop:peek:] (in AppKit) + 69 [0x902f259d]
+ ! : | + ! : | + ! : | 1286 -[NSApplication _realDoModalLoop:peek:] (in AppKit) + 973 [0x902f7497]
+ ! : | + ! : | + ! : | 1286 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] (in AppKit) + 113 [0x90025942]
+ ! : | + ! : | + ! : | 1286 _DPSNextEvent (in AppKit) + 678 [0x900260d8]
+ ! : | + ! : | + ! : | 1286 BlockUntilNextEventMatchingListInMode (in HIToolbox) + 88 [0x917538fa]
+ ! : | + ! : | + ! : | 1285 ReceiveNextEventCommon (in HIToolbox) + 381 [0x91753a8b]
+ ! : | + ! : | + ! : | + 1285 RunCurrentEventLoopInMode (in HIToolbox) + 318 [0x9174c723]
+ ! : | + ! : | + ! : | + 1285 CFRunLoopRunInMode (in CoreFoundation) + 120 [0x95686088]
+ ! : | + ! : | + ! : | + 1285 CFRunLoopRunSpecific (in CoreFoundation) + 332 [0x956861dc]
+ ! : | + ! : | + ! : | + 1227 __CFRunLoopRun (in CoreFoundation) + 1428 [0x95686b04]
+ ! : | + ! : | + ! : | + ! 1227 __CFRunLoopServiceMachPort (in CoreFoundation) + 170 [0x9567d9da]
+ ! : | + ! : | + ! : | + ! 1227 mach_msg (in libsystem_kernel.dylib) + 70 [0x912871f6]
+ ! : | + ! : | + ! : | + ! 1227 mach_msg_trap (in libsystem_kernel.dylib) + 10 [0x91287c22]
+ ! : | + ! : | + ! : | + 23 __CFRunLoopRun (in CoreFoundation) + 1888 [0x95686cd0]
+ ! : | + ! : | + ! : | + ! 16 __CFRunLoopDoTimer (in CoreFoundation) + 743 [0x956a7c37]
+ ! : | + ! : | + ! : | + ! : 16 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ (in CoreFoundation) + 22 [0x956a82a6]
+ ! : | + ! : | + ! : | + ! : 15 TimerVector (in HIToolbox) + 22 [0x91767ee1]
+ ! : | + ! : | + ! : | + ! : | 12 non-virtual thunk to ArpeggiatorPane::userDroppedOrSelectedFileCallback(RhPath*) (in Trilian) + 3080 [0x28b475da]
+ ! : | + ! : | + ! : | + ! : | + 12 SetEventLoopTimerNextFireTime (in HIToolbox) + 105 [0x91767b75]
+ ! : | + ! : | + ! : | + ! : | + 9 CFRunLoopTimerSetNextFireDate (in CoreFoundation) + 632 [0x956a34a8]
+ ! : | + ! : | + ! : | + ! : | + ! 2 __CFRepositionTimerInMode (in CoreFoundation) + 136 [0x956a1ef8]
+ ! : | + ! : | + ! : | + ! : | + ! : 2 __CFRunLoopInsertionIndexInTimerArray (in CoreFoundation) + 245,154 [0x956a20b5,0x956a205a]
+ ! : | + ! : | + ! : | + ! : | + ! 2 __CFRepositionTimerInMode (in CoreFoundation) + 155 [0x956a1f0b]
+ ! : | + ! : | + ! : | + ! : | + ! : 2 CFArrayInsertValueAtIndex (in CoreFoundation) + 173 [0x956a218d]
+ ! : | + ! : | + ! : | + ! : | + ! : 1 _CFArrayReplaceValues (in CoreFoundation) + 320 [0x95659980]
+ ! : | + ! : | + ! : | + ! : | + ! : | 1 __CFTypeCollectionRetain (in CoreFoundation) + 4 [0x9565a114]
+ ! : | + ! : | + ! : | + ! : | + ! : 1 _CFArrayReplaceValues (in CoreFoundation) + 17 [0x95659851]
+ ! : | + ! : | + ! : | + ! : | + ! 2 __CFRepositionTimerInMode (in CoreFoundation) + 298 [0x956a1f9a]
+ ! : | + ! : | + ! : | + ! : | + ! : 2 mk_timer_arm (in libsystem_kernel.dylib) + 10 [0x91287d5a]
+ ! : | + ! : | + ! : | + ! : | + ! 1 __CFRepositionTimerInMode (in CoreFoundation) + 86 [0x956a1ec6]
+ ! : | + ! : | + ! : | + ! : | + ! : 1 CFArrayGetFirstIndexOfValue (in CoreFoundation) + 165 [0x9567b705]
+ ! : | + ! : | + ! : | + ! : | + ! : 1 CFArrayGetValueAtIndex (in CoreFoundation) + 164 [0x9565d1f4]
+ ! : | + ! : | + ! : | + ! : | + ! 1 __CFRepositionTimerInMode (in CoreFoundation) + 123 [0x956a1eeb]
+ ! : | + ! : | + ! : | + ! : | + ! : 1 CFArrayRemoveValueAtIndex (in CoreFoundation) + 158 [0x9566261e]
+ ! : | + ! : | + ! : | + ! : | + ! : 1 _CFArrayReplaceValues (in CoreFoundation) + 372 [0x956599b4]
+ ! : | + ! : | + ! : | + ! : | + ! : 1 __CFArrayReleaseValues (in CoreFoundation) + 495 [0x9565aacf]
+ ! : | + ! : | + ! : | + ! : | + ! 1 __CFRepositionTimerInMode (in CoreFoundation) + 315 [0x956a1fab]
+ ! : | + ! : | + ! : | + ! : | + ! 1 CFRelease (in CoreFoundation) + 457 [0x95654159]
+ ! : | + ! : | + ! : | + ! : | + ! 1 OSAtomicCompareAndSwap32Barrier$VARIANT$mp (in libsystem_c.dylib) + 0 [0x94fc99a4]
+ ! : | + ! : | + ! : | + ! : | + 2 CFRunLoopTimerSetNextFireDate (in CoreFoundation) + 771 [0x956a3533]
+ ! : | + ! : | + ! : | + ! : | + ! 1 pthread_mutex_unlock (in libsystem_c.dylib) + 320 [0x94f7fc4c]
+ ! : | + ! : | + ! : | + ! : | + ! : 1 __mtx_droplock (in libsystem_c.dylib) + 102 [0x94f7f857]
+ ! : | + ! : | + ! : | + ! : | + ! : 1 pthread_threadid_np (in libsystem_c.dylib) + 0 [0x94f81bf8]
+ ! : | + ! : | + ! : | + ! : | + ! 1 pthread_mutex_unlock (in libsystem_c.dylib) + 14 [0x94f7fb1a]
+ ! : | + ! : | + ! : | + ! : | + 1 CFRunLoopTimerSetNextFireDate (in CoreFoundation) + 280 [0x956a3348]
+ ! : | + ! : | + ! : | + ! : | + 1 CFSetGetValues (in CoreFoundation) + 451 [0x9569f513]
+ ! : | + ! : | + ! : | + ! : | + 1 CFBasicHashGetElements (in CoreFoundation) + 121 [0x956615e9]
+ ! : | + ! : | + ! : | + ! : | + 1 CFBasicHashGetBucket (in CoreFoundation) + 24 [0x9565cec8]
+ ! : | + ! : | + ! : | + ! : | 3 non-virtual thunk to ArpeggiatorPane::userDroppedOrSelectedFileCallback(RhPath*) (in Trilian) + 3052 [0x28b475be]
+ ! : | + ! : | + ! : | + ! : | 2 non-virtual thunk to ArpeggiatorPane::userDroppedOrSelectedFileCallback(RhPath*) (in Trilian) + 3019 [0x28b4759d]
+ ! : | + ! : | + ! : | + ! : | ! 1 CVST2AUPluginEntry (in Trilian) + 674 [0x28b49518]
+ ! : | + ! : | + ! : | + ! : | ! : 1 non-virtual thunk to AEffGUIEditor::~AEffGUIEditor() (in Trilian) + 53024 [0x28abd628]
+ ! : | + ! : | + ! : | + ! : | ! : 1 non-virtual thunk to AEffGUIEditor::~AEffGUIEditor() (in Trilian) + 52610 [0x28abd48a]
+ ! : | + ! : | + ! : | + ! : | ! : 1 non-virtual thunk to AEffGUIEditor::~AEffGUIEditor() (in Trilian) + 50733 [0x28abcd35]
+ ! : | + ! : | + ! : | + ! : | ! 1 CVST2AUPluginEntry (in Trilian) + 668 [0x28b49512]
+ ! : | + ! : | + ! : | + ! : | 1 non-virtual thunk to ArpeggiatorPane::userDroppedOrSelectedFileCallback(RhPath*) (in Trilian) + 2996 [0x28b47586]
+ ! : | + ! : | + ! : | + ! : 1 _ZL10FlushTimerP16__CFRunLoopTimerPv (in HIToolbox) + 6 [0x91761a81]
+ ! : | + ! : | + ! : | + ! 4 __CFRunLoopDoTimer (in CoreFoundation) + 675 [0x956a7bf3]
+ ! : | + ! : | + ! : | + ! : 4 mk_timer_arm (in libsystem_kernel.dylib) + 10,5 [0x91287d5a,0x91287d55]
+ ! : | + ! : | + ! : | + ! 1 __CFRunLoopDoTimer (in CoreFoundation) + 1432 [0x956a7ee8]
+ ! : | + ! : | + ! : | + ! : 1 CFSetGetValues (in CoreFoundation) + 1 [0x9569f351]
+ ! : | + ! : | + ! : | + ! 1 __CFRunLoopDoTimer (in CoreFoundation) + 1542 [0x956a7f56]
+ ! : | + ! : | + ! : | + ! : 1 __CFRunLoopFindMode (in CoreFoundation) + 183 [0x95686357]
+ ! : | + ! : | + ! : | + ! : 1 CFSetGetValue (in CoreFoundation) + 135 [0x956771f7]
+ ! : | + ! : | + ! : | + ! : 1 CFBasicHashFindBucket (in CoreFoundation) + 1679 [0x9564d12f]
+ ! : | + ! : | + ! : | + ! : 1 __CFSetStandardHashKey (in CoreFoundation) + 32 [0x9565c9f0]
+ ! : | + ! : | + ! : | + ! : 1 __CFRunLoopModeHash (in CoreFoundation) + 20 [0x95686534]
+ ! : | + ! : | + ! : | + ! : 1 __CFStringHash (in CoreFoundation) + 618 [0x95656c3a]
+ ! : | + ! : | + ! : | + ! 1 __CFRunLoopDoTimer (in CoreFoundation) + 2296 [0x956a8248]
+ ! : | + ! : | + ! : | + 10 __CFRunLoopRun (in CoreFoundation) + 1501 [0x95686b4d]
+ ! : | + ! : | + ! : | + ! 10 mach_port_extract_member (in libsystem_kernel.dylib) + 161 [0x91278966]
+ ! : | + ! : | + ! : | + ! 10 mach_msg (in libsystem_kernel.dylib) + 70 [0x912871f6]
+ ! : | + ! : | + ! : | + ! 10 mach_msg_trap (in libsystem_kernel.dylib) + 10 [0x91287c22]
+ ! : | + ! : | + ! : | + 5 __CFRunLoopRun (in CoreFoundation) + 1316 [0x95686a94]
+ ! : | + ! : | + ! : | + ! 5 mach_port_insert_member (in libsystem_kernel.dylib) + 161 [0x91278a83]
+ ! : | + ! : | + ! : | + ! 5 mach_msg (in libsystem_kernel.dylib) + 70 [0x912871f6]
+ ! : | + ! : | + ! : | + ! 5 mach_msg_trap (in libsystem_kernel.dylib) + 10 [0x91287c22]
+ ! : | + ! : | + ! : | + 4 __CFRunLoopRun (in CoreFoundation) + 2003 [0x95686d43]
+ ! : | + ! : | + ! : | + ! 4 _dispatch_main_queue_callback_4CF (in libdispatch.dylib) + 216 [0x91e7bf2d]
+ ! : | + ! : | + ! : | + ! 4 _dispatch_queue_invoke (in libdispatch.dylib) + 61 [0x91e7b802]
+ ! : | + ! : | + ! : | + ! 4 _dispatch_source_invoke (in libdispatch.dylib) + 688 [0x91e7ee38]
+ ! : | + ! : | + ! : | + ! 4 _dispatch_after_timer_callback (in libdispatch.dylib) + 19 [0x91e7c488]
+ ! : | + ! : | + ! : | + ! 4 _dispatch_call_block_and_release (in libdispatch.dylib) + 15 [0x91e79fc9]
+ ! : | + ! : | + ! : | + ! 4 __-[NSPersistentUIManager init]_block_invoke_2 (in AppKit) + 215 [0x900f3a5f]
+ ! : | + ! : | + ! : | + ! 4 -[NSPersistentUIManager flushPersistentStateAndClose:waitingUntilDone:] (in AppKit) + 201 [0x90083d4b]
+ ! : | + ! : | + ! : | + ! 2 -[NSPersistentUIManager flushAllChangesOptionallyWaitingUntilDone:updatingSnapshots:] (in AppKit) + 1180 [0x90084211]
+ ! : | + ! : | + ! : | + ! : 2 recursivelyEncodeInvalidPersistentState (in AppKit) + 726 [0x90086216]
+ ! : | + ! : | + ! : | + ! : 1 -[NSWindow _copyPublicPersistentUIInfo] (in AppKit) + 635 [0x90087d7b]
+ ! : | + ! : | + ! : | + ! : | 1 -[NSWindow _restorableStateRepresentedURL] (in AppKit) + 70 [0x9074be8f]
+ ! : | + ! : | + ! : | + ! : | 1 -[NSDocument fileURL] (in AppKit) + 186 [0x90225c55]
+ ! : | + ! : | + ! : | + ! : | 1 -[NSURL(NSURL) retain] (in Foundation) + 80 [0x90ab66be]
+ ! : | + ! : | + ! : | + ! : | 1 _CFRetain (in CoreFoundation) + 488 [0x9564da98]
+ ! : | + ! : | + ! : | + ! : | 1 OSAtomicCompareAndSwap32Barrier$VARIANT$mp (in libsystem_c.dylib) + 12 [0x94fc99b0]
+ ! : | + ! : | + ! : | + ! : 1 -[NSWindow _copyPublicPersistentUIInfo] (in AppKit) + 1361 [0x90088051]
+ ! : | + ! : | + ! : | + ! : 1 -[NSWindow _copyWorkspaceIdentifier] (in AppKit) + 46 [0x9008789f]
+ ! : | + ! : | + ! : | + ! : 1 _NSGetWindowWorkspace (in AppKit) + 67 [0x9008790c]
+ ! : | + ! : | + ! : | + ! : 1 CGSGetWindowWorkspaceIgnoringVisibility (in CoreGraphics) + 245 [0x9280bd3f]
+ ! : | + ! : | + ! : | + ! : 1 _CGSGetWindowWorkspaceIgnoringVisibility (in CoreGraphics) + 155 [0x9280bddc]
+ ! : | + ! : | + ! : | + ! : 1 mach_msg (in libsystem_kernel.dylib) + 70 [0x912871f6]
+ ! : | + ! : | + ! : | + ! : 1 mach_msg_trap (in libsystem_kernel.dylib) + 10 [0x91287c22]
+ ! : | + ! : | + ! : | + ! 1 -[NSPersistentUIManager flushAllChangesOptionallyWaitingUntilDone:updatingSnapshots:] (in AppKit) + 732 [0x90084051]
+ ! : | + ! : | + ! : | + ! : 1 dispatch_sync (in libdispatch.dylib) + 45 [0x91e7c8c4]
+ ! : | + ! : | + ! : | + ! : 1 dispatch_barrier_sync_f (in libdispatch.dylib) + 87 [0x91e7c76e]
+ ! : | + ! : | + ! : | + ! : 1 _dispatch_barrier_sync_f_invoke (in libdispatch.dylib) + 30 [0x91e7c2de]
+ ! : | + ! : | + ! : | + ! : 1 __-[NSPersistentUIManager flushAllChangesOptionallyWaitingUntilDone:updatingSnapshots:]_block_invoke_1 (in AppKit) + 2225 [0x90084d48]
+ ! : | + ! : | + ! : | + ! : 1 -[NSPersistentUIManager _updateSnapshotForWindowNumber:forWindowID:encryptionUUID:encryptionKey:encrypt ionKeyGeneration:waitUntilDone:] (in AppKit) + 500 [0x90903b62]
+ ! : | + ! : | + ! : | + ! : 1 -[NSPersistentUIManager snapshotWindow:handler:] (in AppKit) + 526 [0x9008571b]
+ ! : | + ! : | + ! : | + ! : 1 __-[NSPersistentUIManager _updateSnapshotForWindowNumber:forWindowID:encryptionUUID:encryptionKey:encrypt ionKeyGeneration:waitUntilDone:]_block_invoke_1 (in AppKit) + 421 [0x90904c73]
+ ! : | + ! : | + ! : | + ! : 1 try_vm_copy (in AppKit) + 78 [0x90085850]
+ ! : | + ! : | + ! : | + ! : 1 vm_copy (in libsystem_kernel.dylib) + 167 [0x91285a6c]
+ ! : | + ! : | + ! : | + ! : 1 mach_msg (in libsystem_kernel.dylib) + 70 [0x912871f6]
+ ! : | + ! : | + ! : | + ! : 1 mach_msg_trap (in libsystem_kernel.dylib) + 10 [0x91287c22]
+ ! : | + ! : | + ! : | + ! 1 -[NSPersistentUIManager flushAllChangesOptionallyWaitingUntilDone:updatingSnapshots:] (in AppKit) + 1475 [0x90084338]
+ ! : | + ! : | + ! : | + ! 1 dispatch_async (in libdispatch.dylib) + 24 [0x91e7c32e]
+ ! : | + ! : | + ! : | + ! 1 _dispatch_Block_copy (in libdispatch.dylib) + 32 [0x91e79ff2]
+ ! : | + ! : | + ! : | + ! 1 _Block_copy_internal (in libsystem_blocks.dylib) + 155 [0x94bde98a]
+ ! : | + ! : | + ! : | + 3 __CFRunLoopRun (in CoreFoundation) + 1261 [0x95686a5d]
+ ! : | + ! : | + ! : | + ! 1 __CFRunLoopDoObservers (in CoreFoundation) + 384 [0x956b3ff0]
+ ! : | + ! : | + ! : | + ! : 1 pthread_mutex_unlock (in libsystem_c.dylib) + 320 [0x94f7fc4c]
+ ! : | + ! : | + ! : | + ! : 1 OSAtomicCompareAndSwap64Barrier$VARIANT$mp (in libsystem_c.dylib) + 26 [0x94fc99fa]
+ ! : | + ! : | + ! : | + ! 1 __CFRunLoopDoObservers (in CoreFoundation) + 413 [0x956b400d]
+ ! : | + ! : | + ! : | + ! : 1 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ (in CoreFoundation) + 30 [0x956b40ce]
+ ! : | + ! : | + ! : | + ! : 1 LowMemoryNotificationCenter::IsLMNotificationCenterInitialized() (in MACore) + 0 [0x1341600]
+ ! : | + ! : | + ! : | + ! 1 __CFRunLoopDoObservers (in CoreFoundation) + 433 [0x956b4021]
+ ! : | + ! : | + ! : | + ! 1 CFRunLoopObserverInvalidate (in CoreFoundation) + 207 [0x956c327f]
+ ! : | + ! : | + ! : | + ! 1 CFRunLoopRemoveObserver (in CoreFoundation) + 248 [0x956c33f8]
+ ! : | + ! : | + ! : | + ! 1 __CFRunLoopFindMode (in CoreFoundation) + 183 [0x95686357]
+ ! : | + ! : | + ! : | + ! 1 CFSetGetValue (in CoreFoundation) + 157 [0x9567720d]
+ ! : | + ! : | + ! : | + 3 __CFRunLoopRun (in CoreFoundation) + 1813 [0x95686c85]
+ ! : | + ! : | + ! : | + ! 3 CFArrayAppendValue (in CoreFoundation) + 120 [0x95659808]
+ ! : | + ! : | + ! : | + ! 3 -[__NSArrayM addObject:] (in CoreFoundation) + 64 [0x95699770]
+ ! : | + ! : | + ! : | + ! 2 -[__NSArrayM insertObject:atIndex:] (in CoreFoundation) + 1024 [0x95699b80]
+ ! : | + ! : | + ! : | + ! : 1 CFRetain (in CoreFoundation) + 143 [0x9564d89f]
+ ! : | + ! : | + ! : | + ! : 1 _CFRetain (in CoreFoundation) + 168 [0x9564d958]
+ ! : | + ! : | + ! : | + ! 1 -[__NSArrayM insertObject:atIndex:] (in CoreFoundation) + 530 [0x95699992]
+ ! : | + ! : | + ! : | + ! 1 malloc_size (in libsystem_c.dylib) + 71 [0x94fd4d11]
+ ! : | + ! : | + ! : | + ! 1 szone_size (in libsystem_c.dylib) + 131 [0x94f95d54]
+ ! : | + ! : | + ! : | + 2 __CFRunLoopRun (in CoreFoundation) + 1545 [0x95686b79]
+ ! : | + ! : | + ! : | + ! 1 __CFRunLoopDoObservers (in CoreFoundation) + 213 [0x956b3f45]
+ ! : | + ! : | + ! : | + ! : 1 CFArrayGetValueAtIndex (in CoreFoundation) + 114 [0x9565d1c2]
+ ! : | + ! : | + ! : | + ! : 1 -[__NSArrayM objectAtIndex:] (in CoreFoundation) + 62 [0x9567e7be]
+ ! : | + ! : | + ! : | + ! 1 __CFRunLoopDoObservers (in CoreFoundation) + 289 [0x956b3f91]
+ ! : | + ! : | + ! : | + ! 1 pthread_mutex_unlock (in libsystem_c.dylib) + 320 [0x94f7fc4c]
+ ! : | + ! : | + ! : | + ! 1 __mtx_droplock (in libsystem_c.dylib) + 102 [0x94f7f857]
+ ! : | + ! : | + ! : | + ! 1 pthread_threadid_np (in libsystem_c.dylib) + 0 [0x94f81bf8]
+ ! : | + ! : | + ! : | + 2 __CFRunLoopRun (in CoreFoundation) + 1721,1734 [0x95686c29,0x95686c36]
+ ! : | + ! : | + ! : | + 1 __CFRunLoopRun (in CoreFoundation) + 1044 [0x95686984]
+ ! : | + ! : | + ! : | + ! 1 __CFRunLoopDoObservers (in CoreFoundation) + 213 [0x956b3f45]
+ ! : | + ! : | + ! : | + ! 1 CFArrayGetValueAtIndex (in CoreFoundation) + 114 [0x9565d1c2]
+ ! : | + ! : | + ! : | + ! 1 objc_msgSend (in libobjc.A.dylib) + 0 [0x98d3ad30]
+ ! : | + ! : | + ! : | + 1 __CFRunLoopRun (in CoreFoundation) + 1112 [0x956869c8]
+ ! : | + ! : | + ! : | + ! 1 __CFRunLoopDoSources0 (in CoreFoundation) + 116 [0x9565ca74]
+ ! : | + ! : | + ! : | + ! 1 CFSetApplyFunction (in CoreFoundation) + 194 [0x9565ce12]
+ ! : | + ! : | + ! : | + ! 1 CFBasicHashApply (in CoreFoundation) + 52 [0x9565ce54]
+ ! : | + ! : | + ! : | + 1 __CFRunLoopRun (in CoreFoundation) + 1442 [0x95686b12]
+ ! : | + ! : | + ! : | + ! 1 pthread_mutex_lock (in libsystem_c.dylib) + 332 [0x94f7f582]
+ ! : | + ! : | + ! : | + ! 1 pthread_threadid_np (in libsystem_c.dylib) + 53 [0x94f81c2d]
+ ! : | + ! : | + ! : | + 1 __CFRunLoopRun (in CoreFoundation) + 1456 [0x95686b20]
+ ! : | + ! : | + ! : | + ! 1 pthread_mutex_lock (in libsystem_c.dylib) + 20 [0x94f7f44a]
+ ! : | + ! : | + ! : | + 1 __CFRunLoopRun (in CoreFoundation) + 1799 [0x95686c77]
+ ! : | + ! : | + ! : | + ! 1 CFArrayCreateMutable (in CoreFoundation) + 189 [0x9565746d]
+ ! : | + ! : | + ! : | + ! 1 -[__NSPlaceholderArray initWithCapacity:] (in CoreFoundation) + 303 [0x956990ef]
+ ! : | + ! : | + ! : | + ! 1 +[__NSArrayM __new::::] (in CoreFoundation) + 80 [0x95699160]
+ ! : | + ! : | + ! : | + ! 1 __CFAllocateObject2 (in CoreFoundation) + 33 [0x95699451]
+ ! : | + ! : | + ! : | + ! 1 _class_createInstance (in libobjc.A.dylib) + 32 [0x98d45cc5]
+ ! : | + ! : | + ! : | + ! 1 _class_createInstanceFromZone (in libobjc.A.dylib) + 153 [0x98d45c7f]
+ ! : | + ! : | + ! : | + ! 1 calloc (in libsystem_c.dylib) + 41 [0x94fd6827]
+ ! : | + ! : | + ! : | + 1 __CFRunLoopRun (in CoreFoundation) + 2382 [0x95686ebe]
+ ! : | + ! : | + ! : | + 1 __CFRunLoopModeIsEmpty (in CoreFoundation) + 179 [0x9565be03]
+ ! : | + ! : | + ! : | + 1 CFSetContainsValue (in CoreFoundation) + 128 [0x9565bfb0]
+ ! : | + ! : | + ! : | + 1 CFBasicHashGetCountOfKey (in CoreFoundation) + 1614 [0x9565c61e]
+ ! : | + ! : | + ! : | + 1 __CFSetStandardEquateKeys (in CoreFoundation) + 46 [0x956776ee]
+ ! : | + ! : | + ! : | + 1 CFEqual (in CoreFoundation) + 91 [0x9565a29b]
+ ! : | + ! : | + ! : | 1 ReceiveNextEventCommon (in HIToolbox) + 168 [0x917539b6]
+ ! : | + ! : | + ! : | 1 RunCurrentEventLoopInMode (in HIToolbox) + 318 [0x9174c723]
+ ! : | + ! : | + ! : | 1 CFRunLoopRunInMode (in CoreFoundation) + 120 [0x95686088]
+ ! : | + ! : | + ! : | 1 CFRunLoopRunSpecific (in CoreFoundation) + 332 [0x956861dc]
+ ! : | + ! : | + ! : | 1 __CFRunLoopRun (in CoreFoundation) + 1044 [0x95686984]
+ ! : | + ! : | + ! : | 1 __CFRunLoopDoObservers (in CoreFoundation) + 413 [0x956b400d]
+ ! : | + ! : | + ! : | 1 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ (in CoreFoundation) + 30 [0x956b40ce]
+ ! : | + ! : | + ! : | 1 _runLoopObserverWithBlockContext (in CoreFoundation) + 29 [0x956e7ebd]
+ ! : | + ! : | + ! : | 1 __-[NSWindow _postInvalidCursorRects]_block_invoke_1 (in AppKit) + 1135 [0x900efd20]
+ ! : | + ! : | + ! : | 1 -[NSView(NSInternal) _updateTrackingAreas] (in AppKit) + 64 [0x900eff24]
+ ! : | + ! : | + ! : | 1 -[NSFrameView updateTrackingAreas] (in AppKit) + 38 [0x9018f573]
+ ! : | + ! : | + ! : | 1 -[NSWindow(NSWindowResizing) _updateEdgeResizingTrackingAreas] (in AppKit) + 491 [0x9018f788]
+ ! : | + ! : | + ! : | 1 -[NSScreen visibleFrame] (in AppKit) + 24 [0x900937ac]
+ ! : | + ! : | + ! : | 1 _NXVisibleRectForScreen (in AppKit) + 111 [0x90093822]
+ ! : | + ! : | + ! : | 1 _NXLayoutRectForScreen (in AppKit) + 213 [0x9008738a]
+ ! : | + ! : | + ! : | 1 +[_NSWindowFullScreenTransition _fullScreenInstanceInWorkspace:] (in AppKit) + 54 [0x908f1d4f]
+ ! : | + ! : | + ! : | 1 CGSGetWorkspace (in CoreGraphics) + 220 [0x9283a875]
+ ! : | + ! : | + ! : | 1 _CGSGetWorkspace (in CoreGraphics) + 96 [0x9283a8d7]
+ ! : | + ! : | + ! : | 1 mach_msg (in libsystem_kernel.dylib) + 70 [0x912871f6]
+ ! : | + ! : | + ! : | 1 mach_msg_trap (in libsystem_kernel.dylib) + 10 [0x91287c22]
+ ! : | + ! : | + ! : 14 -[NSApplication runModalForWindow:] (in AppKit) + 129 [0x902f6fa3]
+ ! : | + ! : | + ! : 14 std::ostream& TraceOutContainer<CEvs>(std::ostream&, CEvs, char const*, int) (in Logic Pro) + 6010365 [0x5f706d]
+ ! : | + ! : | + ! : 14 -[NSApplication beginModalSessionForWindow:] (in AppKit) + 72 [0x902ee52f]
+ ! : | + ! : | + ! : 14 -[NSProApplication _commonBeginModalSessionForWindow:relativeToWindow:modalDelegate:didEndSelector :contextInfo:] (in ProKit) + 141 [0xfc9f27]
+ ! : | + ! : | + ! : 10 -[NSApplication _commonBeginModalSessionForWindow:relativeToWindow:modalDelegate:didEndSelector :contextInfo:] (in AppKit) + 918 [0x902f6539]
+ ! : | + ! : | + ! : + 8 -[NSApplication _orderFrontModalWindow:relativeToWindow:] (in AppKit) + 782 [0x902f6b2c]
+ ! : | + ! : | + ! : + ! 7 -[NSWindow _doOrderWindow:relativeTo:findKey:forCounter:force:isModal:] (in AppKit) + 459 [0x90125295]
+ ! : | + ! : | + ! : + ! : 7 -[NSWindow _doOrderWindowWithoutAnimation:relativeTo:findKey:forCounter:force:isModal:] (in AppKit) + 79 [0x901255ec]
+ ! : | + ! : | + ! : + ! : 7 -[NSProPanel(_ProSplash) _reallyDoOrderWindow:relativeTo:findKey:forCounter:force:isModal:] (in ProKit) + 147 [0xfcdb47]
+ ! : | + ! : | + ! : + ! : 7 -[NSWindow _reallyDoOrderWindow:relativeTo:findKey:forCounter:force:isModal:] (in AppKit) + 1418 [0x90125b7b]
+ ! : | + ! : | + ! : + ! : 7 -[NSWindow displayIfNeeded] (in AppKit) + 316 [0x90063b8d]
+ ! : | + ! : | + ! : + ! : 6 -[NSView displayIfNeeded] (in AppKit) + 1365 [0x90066dc9]
+ ! : | + ! : | + ! : + ! : | 6 -[NSView _displayRectIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:] (in AppKit) + 4817 [0x9006de9e]
+ ! : | + ! : | + ! : + ! : | 6 -[NSProWindowFrame _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] (in ProKit) + 95 [0xffecb1]
+ ! : | + ! : | + ! : + ! : | 5 -[NSThemeFrame _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVSelect Software Update under the Apple Menu. If no updates are presented, then you are OK.
Helpful Links Regarding Malware Protection
An excellent link to read is Tom Reed's Mac Malware Guide.
Also, visit The XLab FAQs and read Detecting and avoiding malware and spyware.
If you require anti-virus protection I recommend using ClamXav. -
i believe that i have malware (possible highjack of safari browser) on my mac, osx 10.9.4. accordingly, i've tried to run clamxav (on my mac HD) but just get a spinning wheel, then have to shut down. any advice on how to stop spinning wheel or get rid of malware? i have symnatic endpoint and, after scanning, it reveals nothing. please help. :-).
are locked user files or that have incorrect permission a bad thing?
Yes.
why am i removing symantec?
Short answer: Because it's worse than useless and worse than the imaginary "viruses" you're afraid of would be if they really existed. For the long answer, see below.
1. This is a comment on what you should—and should not—do to protect yourself from malicious software ("malware") that circulates on the Internet and gets onto a computer as an unintended consequence of the user's actions. It does not apply to software, such as keystroke loggers, that may be installed deliberately by an intruder who has hands-on access to the computer, or who has been able to log in to it remotely. That threat is in a different category, and there's no easy way to defend against it.
The comment is long because the issue is complex. The key points are in sections 5, 6, and 10.
OS X now implements three layers of built-in protection specifically against malware, not counting runtime protections such as execute disable, sandboxing, system library randomization, and address space layout randomization that may also guard against other kinds of exploits.
2. All versions of OS X since 10.6.7 have been able to detect known Mac malware in downloaded files, and to block insecure web plugins. This feature is transparent to the user. Internally Apple calls it "XProtect."
The malware recognition database used by XProtect is automatically updated; however, you shouldn't rely on it, because the attackers are always at least a day ahead of the defenders.
The following caveats apply to XProtect:
☞ It can be bypassed by some third-party networking software, such as BitTorrent clients and Java applets.
☞ It only applies to software downloaded from the network. Software installed from a CD or other media is not checked.
As new versions of OS X are released, it's not clear whether Apple will indefinitely continue to maintain the XProtect database of older versions such as 10.6. The security of obsolete system versions may eventually be degraded. Security updates to the code of obsolete systems will stop being released at some point, and that may leave them open to other kinds of attack besides malware.
3. Starting with OS X 10.7.5, there has been a second layer of built-in malware protection, designated "Gatekeeper" by Apple. By default, applications and Installer packages downloaded from the network will only run if they're digitally signed by a developer with a certificate issued by Apple. Software certified in this way hasn't necessarily been tested by Apple, but you can be reasonably sure that it hasn't been modified by anyone other than the developer. His identity is known to Apple, so he could be held legally responsible if he distributed malware. That may not mean much if the developer lives in a country with a weak legal system (see below.)
Gatekeeper doesn't depend on a database of known malware. It has, however, the same limitations as XProtect, and in addition the following:
☞ It can easily be disabled or overridden by the user.
☞ A malware attacker could get control of a code-signing certificate under false pretenses, or could simply ignore the consequences of distributing codesigned malware.
☞ An App Store developer could find a way to bypass Apple's oversight, or the oversight could fail due to human error.
Apple has so far failed to revoke the codesigning certificates of some known abusers, thereby diluting the value of Gatekeeper and the Developer ID program. These failures don't involve App Store products, however.
For the reasons given, App Store products, and—to a lesser extent—other applications recognized by Gatekeeper as signed, are safer than others, but they can't be considered absolutely safe. "Sandboxed" applications may prompt for access to private data, such as your contacts, or for access to the network. Think before granting that access. Sandbox security is based on user input. Never click through any request for authorization without thinking.
4. Starting with OS X 10.8.3, a third layer of protection has been added: a "Malware Removal Tool" (MRT). MRT runs automatically in the background when you update the OS. It checks for, and removes, malware that may have evaded the other protections via a Java exploit (see below.) MRT also runs when you install or update the Apple-supplied Java runtime (but not the Oracle runtime.) Like XProtect, MRT is effective against known threats, but not against unknown ones. It notifies you if it finds malware, but otherwise there's no user interface to MRT.
5. The built-in security features of OS X reduce the risk of malware attack, but they are not, and never will be, complete protection. Malware is a problem of human behavior, and a technological fix is not going to solve it. Trusting software to protect you will only make you more vulnerable.
The best defense is always going to be your own intelligence. With the possible exception of Java exploits, all known malware circulating on the Internet that affects a fully-updated installation of OS X 10.6 or later takes the form of so-called "Trojan horses," which can only have an effect if the victim is duped into running them. The threat therefore amounts to a battle of wits between you and the scam artists. If you're smarter than they think you are, you'll win. That means, in practice, that you always stay within a safe harbor of computing practices. How do you know when you're leaving the safe harbor? Below are some warning signs of danger.
Software from an untrustworthy source
☞ Software of any kind is distributed via BitTorrent, or Usenet, or on a website that also distributes pirated music or movies.
☞ Software with a corporate brand, such as Adobe Flash Player, doesn't come directly from the developer’s website. Do not trust an alert from any website to update Flash, or your browser, or any other software.
☞ Rogue websites such as Softonic and CNET Download distribute free applications that have been packaged in a superfluous "installer."
☞ The software is advertised by means of spam or intrusive web ads. Any ad, on any site, that includes a direct link to a download should be ignored.
Software that is plainly illegal or does something illegal
☞ High-priced commercial software such as Photoshop is "cracked" or "free."
☞ An application helps you to infringe copyright, for instance by circumventing the copy protection on commercial software, or saving streamed media for reuse without permission.
Conditional or unsolicited offers from strangers
☞ A telephone caller or a web page tells you that you have a “virus” and offers to help you remove it. (Some reputable websites did legitimately warn visitors who were infected with the "DNSChanger" malware. That exception to this rule no longer applies.)
☞ A web site offers free content such as video or music, but to use it you must install a “codec,” “plug-in,” "player," "downloader," "extractor," or “certificate” that comes from that same site, or an unknown one.
☞ You win a prize in a contest you never entered.
☞ Someone on a message board such as this one is eager to help you, but only if you download an application of his choosing.
☞ A "FREE WI-FI !!!" network advertises itself in a public place such as an airport, but is not provided by the management.
☞ Anything online that you would expect to pay for is "free."
Unexpected events
☞ A file is downloaded automatically when you visit a web page, with no other action on your part. Delete any such file without opening it.
☞ You open what you think is a document and get an alert that it's "an application downloaded from the Internet." Click Cancel and delete the file. Even if you don't get the alert, you should still delete any file that isn't what you expected it to be.
☞ An application does something you don't expect, such as asking for permission to access your contacts, your location, or the Internet for no obvious reason.
☞ Software is attached to email that you didn't request, even if it comes (or seems to come) from someone you trust.
I don't say that leaving the safe harbor just once will necessarily result in disaster, but making a habit of it will weaken your defenses against malware attack. Any of the above scenarios should, at the very least, make you uncomfortable.
6. Java on the Web (not to be confused with JavaScript, to which it's not related, despite the similarity of the names) is a weak point in the security of any system. Java is, among other things, a platform for running complex applications in a web page, on the client. That was always a bad idea, and Java's developers have proven themselves incapable of implementing it without also creating a portal for malware to enter. Past Java exploits are the closest thing there has ever been to a Windows-style virus affecting OS X. Merely loading a page with malicious Java content could be harmful.
Fortunately, client-side Java on the Web is obsolete and mostly extinct. Only a few outmoded sites still use it. Try to hasten the process of extinction by avoiding those sites, if you have a choice. Forget about playing games or other non-essential uses of Java.
Java is not included in OS X 10.7 and later. Discrete Java installers are distributed by Apple and by Oracle (the developer of Java.) Don't use either one unless you need it. Most people don't. If Java is installed, disable it—not JavaScript—in your browsers.
Regardless of version, experience has shown that Java on the Web can't be trusted. If you must use a Java applet for a task on a specific site, enable Java only for that site in Safari. Never enable Java for a public website that carries third-party advertising. Use it only on well-known, login-protected, secure websites without ads. In Safari 6 or later, you'll see a lock icon in the address bar with the abbreviation "https" when visiting a secure site.
Stay within the safe harbor, and you’ll be as safe from malware as you can practically be. The rest of this comment concerns what you should not do to protect yourself.
7. Never install any commercial "anti-virus" (AV) or "Internet security" products for the Mac, as they are all worse than useless. If you need to be able to detect Windows malware in your files, use one of the free security apps in the Mac App Store—nothing else.
Why shouldn't you use commercial AV products?
☞ To recognize malware, the software depends on a database of known threats, which is always at least a day out of date. This technique is a proven failure, as a major AV software vendor has admitted. Most attacks are "zero-day"—that is, previously unknown. Recognition-based AV does not defend against such attacks, and the enterprise IT industry is coming to the realization that traditional AV software is worthless.
☞ Its design is predicated on the nonexistent threat that malware may be injected at any time, anywhere in the file system. Malware is downloaded from the network; it doesn't materialize from nowhere. In order to meet that nonexistent threat, commercial AV software modifies or duplicates low-level functions of the operating system, which is a waste of resources and a common cause of instability, bugs, and poor performance.
☞ By modifying the operating system, the software may also create weaknesses that could be exploited by malware attackers.
☞ Most importantly, a false sense of security is dangerous.
8. An AV product from the App Store, such as "ClamXav," has the same drawback as the commercial suites of being always out of date, but it does not inject low-level code into the operating system. That doesn't mean it's entirely harmless. It may report email messages that have "phishing" links in the body, or Windows malware in attachments, as infected files, and offer to delete or move them. Doing so will corrupt the Mail database. The messages should be deleted from within the Mail application.
An AV app is not needed, and cannot be relied upon, for protection against OS X malware. It's useful, if at all, only for detecting Windows malware, and even for that use it's not really effective, because new Windows malware is emerging much faster than OS X malware.
Windows malware can't harm you directly (unless, of course, you use Windows.) Just don't pass it on to anyone else. A malicious attachment in email is usually easy to recognize by the name alone. An actual example:
London Terror Moovie.avi [124 spaces] Checked By Norton Antivirus.exe
You don't need software to tell you that's a Windows trojan. Software may be able to tell you which trojan it is, but who cares? In practice, there's no reason to use recognition software unless an organizational policy requires it. Windows malware is so widespread that you should assume it's in everyemail attachment until proven otherwise. Nevertheless, ClamXav or a similar product from the App Store may serve a purpose if it satisfies an ill-informed network administrator who says you must run some kind of AV application. It's free and it won't handicap the system.
The ClamXav developer won't try to "upsell" you to a paid version of the product. Other developers may do that. Don't be upsold. For one thing, you should not pay to protect Windows users from the consequences of their choice of computing platform. For another, a paid upgrade from a free app will probably have all the disadvantages mentioned in section 7.
9. It seems to be a common belief that the built-in Application Firewall acts as a barrier to infection, or prevents malware from functioning. It does neither. It blocks inbound connections to certain network services you're running, such as file sharing. It's disabled by default and you should leave it that way if you're behind a router on a private home or office network. Activate it only when you're on an untrusted network, for instance a public Wi-Fi hotspot, where you don't want to provide services. Disable any services you don't use in the Sharing preference pane. All are disabled by default.
10. As a Mac user, you don't have to live in fear that your computer may be infected every time you install software, read email, or visit a web page. But neither can you assume that you will always be safe from exploitation, no matter what you do. Navigating the Internet is like walking the streets of a big city. It's as safe or as dangerous as you choose to make it. The greatest harm done by security software is precisely its selling point: it makes people feel safe. They may then feel safe enough to take risks from which the software doesn't protect them. Nothing can lessen the need for safe computing practices. -
My ipod touch shut down for no reason. now when i try to turn it on again, it goes to the apple icon to the spinning wheel, then it repeats.
Try:
- iOS: Not responding or does not turn on
- Also try DFU mode after try recovery mode
How to put iPod touch / iPhone into DFU mode « Karthik's scribblings
- If not successful and you can't fully turn the iOS device fully off, let the battery fully drain. After charging for an least an hour try the above again.
- Try another cable
- Try on another computer
- If still not successful that usually indicates a hardware problem and an appointment at the Genius Bar of an Apple store is in order.
Apple Retail Store - Genius Bar -
After software update, my Mac Pro 13 has grey screen, spinning but won't re-boot
After update my Mac Pro 13 will not reboot. Grey screen, spinning icon but nothing I tried works.
If your computer is stuck restarting, hold the Power button to turn off your MacBook Pro and turn it on again. As the installation finished previously, nothing will get damaged
-
When I tried a custom leopard install(omitting all but canon printers), a window appeared that " I could not install OSX ON THIS DISK." I tried a full install again and a window appeared stating that " the HD was not formatted properly, would I like reformat in hfs extended HFS EXTENDED journalled and ERASE THE HD?" I use disk utility on leopard to reset the iMac to restart from the original Tiger OS on the HD, & that was when it refused to boot. During 1 attempt I even tried to boot with the C key held for many minutes to start fron the Tiger OS disk but the iMac wouldn't start the cd spinning. I did hear that familiar FIRMWARE UPDATE CHIME! but I was not upgrading firmware as none was downloaded, and Leopard did not tell me it required a firmware update first, when I attempted to install it. So: I get the chime when the power button is pressed. Option key finds the HD TIGER AND THE CD 's Tiger. I van choose both. But neither boots. Starting with the C key held doesn't boot. In every case the startup grey screen appears with the grey startup pinwheel, this continues for many minutes. Then it shuts itself off. Help help help. My son has Graduate School papers in progress, and I just fried his iMac. Thanks to all.
Simon:
Thanks very much for the suggestions! I tried your method of booting to the install CD while holding option (alt), and then running Disk Utility to repair the disk and the permissions. Even though it still told me the drive didn't need repairing, there were more permissions that needed repairing when booting this way (as opposed to when booting while holding the C key.)
Anyhow, after doing this, my computer restarted just fine from the hard drive. Mail works now and I'm about to try repairing permissions one more time, then shutting down and restarting again, this time without doing it from the install CD. Wish me luck...
OK. It booted up perfectly this time. I'm not quite sure why that worked, though. Anyone care to illuminate me as to why booting while holding option (alt) let Disk Utility do what it needed to, while booting while holding C didn't?
At this point I'm just curious. My problem has been solved!
Thanks again very much, Simon. I really appreciate it, mate.
Cheers,
--forkboy
iMac G5 20" Mac OS X (10.4.9) -
MacBook won't start up just getting a grey screen and wheel spins
My MacBook will not go pass the boot up screen (grey screen with apple logo) the wheel just keeps spinning. What can I do to fix this ?
I assume you do not have Lion or later installed. What do you have - Snow Leopard? If so, then try this instead:
Reinstall OS X without erasing the drive
1. Repair the Hard Drive and Permissions
Boot from your Snow Leopard Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Utilities menu. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer.
If DU reports errors it cannot fix, then you will need Disk Warrior and/or Tech Tool Pro to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
2. Reinstall Snow Leopard
If the drive is OK then quit DU and return to the installer. Proceed with reinstalling OS X. Note that the Snow Leopard installer will not erase your drive or disturb your files. After installing a fresh copy of OS X the installer will move your Home folder, third-party applications, support items, and network preferences into the newly installed system.
Download and install Mac OS X 10.6.8 Update Combo v1.1.
Maybe you are looking for
-
Arrays touching on front panel slows down VI.
I have written a VI which downloads and displays 2 Arrays of Spacecraft Telemetry packets. If I arrange the arrays on the front panel so that they are touching (to look neater), the VI slows to a fraction of its original speed. Why is this? I wasted
-
TS2634 IOS6 error message Accessory unavailable uses too much power
IOS6 has stopped me from using my apple access connector that loads photos direct from memory card. Error message ,uses to much power. This worked fine on my iPad 2 until I upgraded, any suggestions how to fix this?
-
Difference between storing sysdate and to_date(to_char(sysdate, 'DD Mon YYY
What is the difference between storing sysdate or to_date(to_char(sysdate, 'DD Mon YYYY HH:MI AM'),'DD Mon YYYY HH:MI AM') in a date data type column? When I column value is set with sysdate the following query gives no records select * from Test WHE
-
Non riesco a convertire un pdf in word perchè mi dice che si è verificato un errore che ha interrotto l'elaborazione del pdf. Chi mi può aiutare? Grazie.
-
I was downloading a rented movie but could not finish the download before I had to board a plane. I went to play the movie on the plane but received an error message and could not watch it. I was charged for the rental. Can I get a credit?