This problem is due to the protection, the sandboxing.
Various approaches have been suggested on the online forums, including editing the config files to be more lenient about these protections (the so called "alternative approach" proposed by the poster)
I tried them all, never had any result. I almost gave up, then read about that safe mode reboot suggestion. I have long uptimes and I don't want to bother reopening stuff, so I didn't do it immediately.
But finally I did, and it worked. Based on the timestamp of my blog (http://en.blog.guylhem.net/) I tried that on mar 31, about 1 month ago, and here are the results from the syslog so far (1 month of data after the fix):
lsboxd sqweaked only once in a month - and for something different.
I'd call this "problem solved", which is supported by my personal observation over this last month : I haven't experienced the problem again yet, while previously it was at least every 2 days (along with the TimeMachine always reindexing)
My suggestion: check your logs with the greps, try this simple fix and report your results in a month.
EDIT: This in on my macbookair with a 480GB OWC SSD (but apparently it also occurs on macbookair with vanilla apple ssds). I used istat menus, and still do. I didn't disable the dynamic pager, spotlight or anything else.
(EDIT2: removed) - thanks for the 4 spaces suggestion! as explained, the simple safe reboot solution made the problem go away, while other approaches didn't. It works for me, and I have 1 month of data supporting that.
> This problem is due to the protection, the sandboxing.
The problem of sandbox violation lines appearing in your Console is caused by sandboxing. It's unlikely that it goes any further than that.
The author has associated some other silent issue with his system to this one sandbox violation just because it happens to be printed all the time.
If you're experiencing some performance problem, run sysdiagnose(1) (or hit the key combo in its man page) and throw it into Apple's bug reporter. Or, if you stare at the output for a very long time, you might even figure out how to read it.
Various approaches have been suggested on the online forums, including editing the config files to be more lenient about these protections (the so called "alternative approach" proposed by the poster)
I tried them all, never had any result. I almost gave up, then read about that safe mode reboot suggestion. I have long uptimes and I don't want to bother reopening stuff, so I didn't do it immediately.
But finally I did, and it worked. Based on the timestamp of my blog (http://en.blog.guylhem.net/) I tried that on mar 31, about 1 month ago, and here are the results from the syslog so far (1 month of data after the fix):
About 97 issues of sandboxing zealousness remain, if we distinct them by removing the PIDs with : This last one is interesting : lsboxd sqweaked only once in a month - and for something different.I'd call this "problem solved", which is supported by my personal observation over this last month : I haven't experienced the problem again yet, while previously it was at least every 2 days (along with the TimeMachine always reindexing)
My suggestion: check your logs with the greps, try this simple fix and report your results in a month.
EDIT: This in on my macbookair with a 480GB OWC SSD (but apparently it also occurs on macbookair with vanilla apple ssds). I used istat menus, and still do. I didn't disable the dynamic pager, spotlight or anything else.
(EDIT2: removed) - thanks for the 4 spaces suggestion! as explained, the simple safe reboot solution made the problem go away, while other approaches didn't. It works for me, and I have 1 month of data supporting that.