Sometimes when accessing native system applications such as TextEdit, we see that when trying to open, save or modify files we get a warning of the denial of permission to open the file in question or simply that it could not be saved since it is currently being edited. There may even be strange cases where more than one identical file can accumulate on the hard disk identified with the suffix "sb" followed by an identifier for the application in question, an example would be "Sb-67d1h723-HUYxOl".
The sandbox is a method of increasing security as much as possible by "setting aside" the application from the main resources of the operating system, only those that the developer specifically adds, without it being able to modify any system value, putting the integrity of the rest at risk. Something like running each application in different modules instead of in a common "yard".
But sometimes the service or daemon in charge of sandboxing does not work as well as it should, so we find that when errors occur in it, sometimes restricts permissions it shouldn'tTherefore, a priori tasks as simple as saving a document or editing it become a problem.
So if you come across in this specific case, where there is a problematic application that does not let you save documents, we must first try something more specific before we jump into trying to fix it using disk utility with global permission repair or looking at file system corruptions.
So we must open the console in the path, Macintosh HD> Applications> Utilities> Console or directly looking for it in spotlight. Once this is done, we will look for the "sandboxd" daemon which is the process that controls the general sandboxing of the system.
With the console open and the process located, it is best to relaunch the problematic application to check if there are more errors, if we see that errors continue to occur, we will try to force the application exit to throw it again. If these still do not get anything, we will restart the Mac since supposedly this should solve the problem by also restarting the background process that is failing.
To make sure we will look for the container of the application that is by pressing and holding the key OTHER as we head to the menu Ir in the top bar of the finder, then the library option will appear and in the containers folder we will locate the container of the problematic sandbox which we will delete since it is nothing more than a duplicate of the structure that we have in the program container located in applications. In this way we force the system to recreate it once we restart. With this we should be able to solve many sandboxing problems that occur in some programs. If this is not effective, then we can continue with more general steps.
More information - Possible solution to two small problems in Mountain Lion 10.8.3
Source - Cnet