1 2 Previous Next 23 Replies Latest reply: Jun 30, 2013 1:54 AM by AndrewMacintosh Go to original post
  • 15. Re: Sandboxd error messages
    randy_harris Level 1 Level 1 (0 points)

    I am also ving these errors but did not restore, in fact I recently did a clean installation of Mountain Lion on my iMac.


    sandboxd: ([624]) com.apple.qtkits(624) deny file-read-data /Users/randyharris/Storage/Scratch/MediaPrep/iFlicks


    many errors in console like the above, this happens when I move media files on my system, and or try to launch an AppleScript via Folder Actions to move these media files.

  • 16. Re: Sandboxd error messages
    kristin119 Level 1 Level 1 (15 points)

    I had similar mdworker and sandbox error on my machines after installing Mountain Lion. Following instructions elsewhere in these forums from Linc Davis I was able to eliminate most of the messages.


    1. Restart the machine in Safe Mode. (hold down the shift key after you hear the restart tone).


    2. After the machine is completely restarted, Restart again to enter the normal mode.


    That's it.


    I still get


    1/23/13 9:22:31.000 AM kernel[0]: Sandbox: sandboxd(101) deny mach-lookup com.apple.coresymbolicationd


    But the rest of the mdworker and lsboxd messages are gone.

  • 17. Re: Sandboxd error messages
    Mac_o_phile Level 1 Level 1 (0 points)

    Do what Kristin said. Shold mark her reply as helpful at least too.

  • 18. Re: Sandboxd error messages
    Michael_505 Level 1 Level 1 (0 points)

    No, I tried this, but since I use FileVault, I had to decrypt the entire drive before it would safe boot (which causes Time Machine to notice that every single file has changed, so it now wants to delete all of my old backups, so my only option is to buy more hard drives if I want to keep the old backups -- very nice Apple, thanks).


    After I safe booted, the messages were temporarily gone. But then after about a day of normal document editing, they are back. Since they were once gone, I turned FileVault back on, which means that in order to safe boot again I have to do another full backup (that takes all day).


    There are a pile of serious bugs here that Apple needs to resolve ASAP. I can't believe I wasted so much time with such a crappy product that cost so much money. Never again.

  • 19. Re: Sandboxd error messages
    knasher Level 1 Level 1 (0 points)

    I've been having exactly the same mesages!


    I'm gonna be verbose here, as I'm a fairly seasoned mac user who can usually can fix my mac using one or of the usual fixes – permissions/pram/safeboot/disk repair etc... and I'm very aware that the console is a mine field of cryptic information, most of which you could convince yourself might be worrying but is generally entirely benign. But I'm not chasing console ghosts here, my installation of Mountain Lion is unstable. and it's with some frustration that I've tried all of these and still have random console messages and random serious system instability to which there is no pattern as to when these errors and instability occour.


    In frustration I've experimented with both my macs as they're both having the same issues with the same messages: again, it's really very random: I've noticed that sometimes these errors can pop up within hours of using a totally fresh mac, not installing anything just surfing the net and adding e-mail accounts... but sometimes you get stable activity and clear consoles for weeks even once all my usual software is on and i've been busy working when suddenly it'll hang out of the blue.


    I can replicate this behaviour on my Early 2008 Mac Pro (12gb Memory/2x2.8QUAD ZEON/ATI RADION HD 5770 1024MB/4 HDDs 2 x internal 1TB drives original to the machine, 250gb drive for archiving which is usually left unmounted, and one attached Lacie External on the Firewire 800) and my MacBook (original unibody MacBook... don't have the spec in front of me, but as orginal spec but with faster newer harder drive) Both running OS X 10.8.4 (12E55).


    These console messages are constant, appear no matter what programmes are open or closed and are often very apprenent when the machine is experiencing slowness, hangs, failures to shut down, sudden total crashes of the OS (the cursor moves but nothing will respond, no amount of time resolves the hang, and no kernal panic or obvious error message in the console appears, or occasionally a sudden slowdown, followed by a hang where apps cannot be used or launched but finder can be used*.


    I really don't know what to do: the hardware is fine – it's been checked, and either way it's happening across different machines of radically different component builds.


    These pop up all the time without any good explanation, they're the only ones that are consistent to both macs,


    • kernel[0]: Sandbox: sandboxd(1739) deny mach-lookup com.apple.coresymbolicationd
    • Safari[1080]: CGContextClipToRect: invalid context 0x0
    • coreaudiod[158]: Enabled automatic stack shots because audio IO is inactive
    • coreaudiod[158]: Disabled automatic stack shots because audio IO is active
      apsd[62]: <APSConnectionNotificationQueue: 0x7f8afb807300>: outstanding count -1 for com.apple.apsd-queue-port=com.apple.SocialPushAgent-user=501-env=production
    • com.apple.usbmuxd[25]: _heartbeat_failed heartbeat detected detach for device 0x10-!

      The coreaudiod ones are new... they appeared at the last OS update, but again they've become frequent and constant features of the console generating thousands of lines a day...


    The messages above occur frequently and constantly, and they appear whether the mac is being used or is standing idle... it's driving me up the wall as these system hangs and crashes continue to slow down my workflow, lose my work (you can only save/autosave so often before OCD kicks in!) or just generally inconvience my general daily usage and enjoyment of my mac... There really is no other indication in the logs that the machines are experiencing issues and having tried all of the usual mac fixes as the length and verbosity of this post probably suggests I'm really quite desperately clutching at straws to gain back the system integrity and stability that's made me buy macs for most of my adult life...




    Any help, gratefully received!



    *This specifically occurs when the time machine was backing up and a file transfer between the internal HDDs has been in progress - this last eventually resolves itself once the backup routine finally responds to the 'x' being clicked to stop the backup: (I'd force it to stop as it takes a good 15/20 minutes on the few ocassions it's happened to actually sort itself out, but you can't launch force quit or activity monitor or terminal to do so)... after this specific hang, the console will be entirely blank, literally as if nothing has happened at all in the system since it initially hung: solved this last one by not backing up to the TimeMachine... not the ideal fix, but it did solve that specific issue, and it's left me with an expensive white door stop as well.

  • 20. Re: Sandboxd error messages
    Mac_o_phile Level 1 Level 1 (0 points)

    The coreaudio messages are new to me too. I fixed the sandbox messages using this trick:


    I found the following three errors message keep showing up in the system log (by going to "Applications" -> "Utilities" -> "Console" and select the "All Messages".)


    mdworker[1626]: Unable to talk to lsboxd

    sandboxd[1633]: ([1631]) mdworker(1631) deny mach-lookup com.apple.ls.boxd

    kernel[0]: Sandbox: sandboxd(1627) deny mach-lookup com.apple.coresymbolicationd




    I don't know and I don't care. It's better to leave it to Apple to explain it to its customers.




    Step 1: Modify the system configure file (you need to be root to do so). Edit the /System/Library/Sandbox/Profiles/system.sb file to append the following three lines at the end:


    ;;; FixSandboxErrors

    (allow mach-lookup (global-name "com.apple.ls.boxd"))

    (allow mach-lookup (local-name "com.apple.ls.boxd"))


    Step 2: Clear the cache (you need to be root to do so) by running the following command.


    rm -fr /System/Library/Caches/*


    Step 3: Safeboot the Mac.

    - Shutdown the Mac first (remember to enable speaker volume before shutdown).

    - Start up the Mac. Just after the startup tone (cannot do it before the tone), press and hold the shift key.

    - When the grey apply logo appears, release the shift key.

    - After the system is up to the login screen, confirm that there is a red "safeboot" label at the upper right screen corner.

    - Then you can simply restart the Mac.


    I tried the fix that others say works, booting into safe mode, but the messages kept coming back until I did the procedure above. Now the sandbox messages are gone but, I'm not sure if modifying system.sb is such a great idea, I don't know that much about it.


    Credit to the original source: http://khtsoi.blogspot.com/2012/10/macbook-air-fan-goes-crazy.html

    (Scroll down the page about 1/2 way)

  • 21. Re: Sandboxd error messages
    knasher Level 1 Level 1 (0 points)

    I've just updated the system.sb file after reading this info here and elsewhere, thank you - that particular fix does has seemed to have stopped the kernel[0]: Sandbox: sandboxd(1739) deny mach-lookup com.apple.coresymbolicationd emessages, and indeed the boot time from cold to login to desktop was noticably quicker.


    Fingers crossed for a more stable system.

  • 22. Re: Sandboxd error messages
    knasher Level 1 Level 1 (0 points)

    Also forgot to mention another frequent visitor to my console of doom.


    sandboxd[1598]: ([1589]) com.apple.qtkits(1589) deny file-read-data /Volumes/ -drivename/ -folder

  • 23. Re: Sandboxd error messages
    AndrewMacintosh Level 1 Level 1 (20 points)

    Whilst this won't solve your problem, that Safari error (Invalid Context) is serious.


    In 10.9, the console is more specific with this message and says;


    'Safari: CGContextClipToRect: Invalid Context0x0. This is a serious error. This application, or the library it uses is using an invalid context and is thereby contributing to an overall contribution of system stability and reliability. This notice is courtesy: please fix this problem. It will become a fatal error in an upcoming update.'

1 2 Previous Next