что такое com.apple.coresymbolicationd в кешах?
Выполняю некоторую очистку моего Macbook Air со 128 SSD в поисках больших файлов, чтобы уменьшить используемое пространство. Я нашел что-то с именем com.apple.coresymbolicationd, объемом 1 ГБ, в папке library / caches, которую я не помню раньше. Бегущий Горный Лев
Что это, есть ли способ это очистить?
Кстати, я использую DaisyDisk, чтобы показать файлы и размеры
Обозначение означает замену адресов памяти символами (например, функциями или переменными) или, например, добавление имен функций и информации о номерах строк. Он используется для отладки и анализа отчетов о сбоях.
/System/Library/Caches/com.apple.coresymbolicationd/data было также около 600 МБ на моем счете, так что я думаю, это нормально. Удаление файлов в папках кэша обычно безопасно и /System/Library/Caches/ даже исключено из резервных копий Time Machine.
Файлы, хранящиеся в системной и пользовательской папках Caches, предназначены для ускорения работы вашего Mac, и процесс будет воссоздавать их, если вы решите переместить их в корзину и перезагрузить компьютер.
Большинство программ ведут себя достаточно хорошо, чтобы справиться с удалением файлов из-под работающей системы, но я также приобрел привычку перемещать их в корзину и затем перезагружать, чтобы система могла заново создавать новые папки, если это необходимо, перед удалением файлов.
Этот основной демон практически не документирован Apple, и один файл данных, вероятно, является зашифрованным файлом базы данных sqlite3 (или каким-либо другим хранилищем двоичных данных) для внутреннего использования ОС для управления процессами. Вы можете посмотреть на исходный код и системные заголовки, которые принадлежат CoreSymbolication здесь, поскольку он взаимодействует с источником для dtrace :
Источник
Файл com.apple.coresymbolicationd объемом 9 ГБ в кэше
Я пытаюсь освободить место на диске, и я столкнулся с этим:
Я читал отчеты о файле 600M или файле 1GB, но никогда ничего подобного.
Безопасно ли удалять или перезагрузка часто помогает очистить некоторые из этих файлов?
Используя вещи из этой ссылки ( http://www.macobserver.com/tmo/article/how_to_recover_missing_hard_drive_space/ ) я нашел файл — com.apple.coresymbolicationd объемом 133 ГБ.
Чтобы удалить, загрузитесь в безопасном режиме (Cmd-S до появления логотипа Apple), запустите проверку файловой системы, подключите диск, а затем просто sudo rm файл
Нет. Перезагрузка не очищает файлы кэша в системе. Вам необходимо разобраться, какая именно подсистема создает здесь кэши, и определить, есть ли способ их ручной очистки или перемещения в корзину, а затем перезагрузить компьютер, чтобы увидеть, когда / как / какого размера они воссоздаются.
Я бы загрузился в однопользовательском режиме и использовал, rm чтобы очистить этот файл, так как тогда его никто не использовал. Вы также можете использовать, sudo mv /System/Library/Caches/com.apple.coresymbolicationd/data /tmp а затем перезагрузить компьютер. После перезагрузки вы можете удалить файл с /tmp помощью sudo rm /tmp/data .
Я догадываюсь, что у вас установлен XCode и вы добавили большое количество символов в вашу базу данных из одной или нескольких версий iOS, чтобы XCode мог символизировать аварийные дампы, чтобы помочь в отладке приложений с использованием XCode. Однако это также может быть ошибкой, и всякий раз, когда подсистема начинает перерабатывать кэш, она сама очищается. Если вы можете ограничить количество SDK, который вы используете в XCode, это также может помочь. Мне кажется, что люди с 60-миллиметровыми файлами не используют XCode, те, у кого есть 1 МБ разработчика для одной версии iOS за раз, и те, у кого базы данных большего размера, активируют несколько OS X и iOS SDK из Xcode.
Источник
Question: Q: coresymbolicationd: whazzup?
Dear forum pals,
the system log of my MacBook Air (2012 model, I recently installed 10.11 aka El Capitan) is filled with the following:
13/10/2015 20:12:14.000 kernel[0]: Sandbox: coresymbolicatio(22974) System Policy: deny(1) file-write-create /System/Library/Caches/com.apple.coresymbolicationd
13/10/2015 20:12:14.301 coresymbolicationd[22974]: /System/Library/Caches/com.apple.coresymbolicationd/data does not exist, resetting cache
13/10/2015 20:12:14.301 coresymbolicationd[22974]: Attempt to create [/System/Library/Caches/com.apple.coresymbolicationd/data] failed. No such file or directory
13/10/2015 20:12:14.301 coresymbolicationd[22974]: Unable to open storage at /System/Library/Caches/com.apple.coresymbolicationd/data
13/10/2015 20:12:14.304 com.apple.xpc.launchd[1]: (com.apple.coresymbolicationd) Service only ran for 0 seconds. Pushing respawn out by 10 seconds.
From what I can get, something is trying to write this com.apple.coresymbolicationd file in System/Library/Caches, but the new OS 10.11 does not allow it.
In fact, if I check in that directory, the folder/file does not exist.
I tried to delete caches and reboot. I tried to boot in safe mode and then reboot. No way.
What would you suggest to check to fix this issue? How to find the culprit which is trying to write this file?
Thanks for any help/hint.
OS X El Capitan (10.11)
Posted on Oct 13, 2015 11:20 AM
All replies
Loading page content
Page content loaded
This procedure is a diagnostic test. It makes no changes to your data.
Please triple-click anywhere in the line below on this page to select it:
ls -@Oaen /S*/*/Caches | pbcopy
Copy the selected text to the Clipboard by pressing the key combination command-C .
Launch the built-in Terminal application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U . The application is in the folder that opens.
☞ Open LaunchPad and start typing the name.
Paste into the Terminal window by pressing the key combination command-V . I’ve tested these instructions only with the Safari web browser. If you use another browser, you may have to press the return key after pasting.
Wait for a new line ending in a dollar sign ($) to appear below what you entered.
The output of the command will be automatically copied to the Clipboard. If the command produced no output, the Clipboard will be empty. Paste into a reply to this message.
The Terminal window doesn’t show the output. Please don’t copy anything from there.
If any personal information appears in the output, anonymize before posting, but don’t remove the context.
Oct 13, 2015 6:13 PM
Hi, Davis. This is the output:
drwxr-xr-x 6 0 0 restricted 204 4 Oct 13:02 .
drwxr-xr-x 79 0 0 restricted 2686 4 Oct 12:56 ..
drwxr-xr-x 6 0 0 restricted 204 4 Oct 13:02 com.apple.CVMS
drwxr-xr-x 3 0 0 restricted 102 4 Oct 12:59 com.apple.bootstamps
drwxr-xr-x 2 0 0 restricted 68 4 Oct 12:59 com.apple.corestorage
drwxr-xr-x 4 0 0 restricted 136 4 Oct 12:56 com.apple.kext.caches
What does it mean?
Thanks for helping!
Oct 13, 2015 11:22 PM
It means that the OS X installation is corrupt. Have you modified any built-in configuration files?
Oct 14, 2015 6:21 AM
No, I didn’t, or at least not intentionally.
Since I purchased a new SSD, I did a clean install of el capitan booting from an external USB key, formatted SSD and then I installed the OS.
During the installation I was asked to connect to a timemachine backup, which I did to move on the new mac the backup content.
Maybe it just took over something from the timemachine backup done on the previous mac over yosemite.
What if I re-download 10.11 and I reinstall it on the top of the current installation?
Thanks for helping in solving this issue!
Oct 14, 2015 6:28 AM
I’m trying to understand how this could have happened. Please triple-click anywhere in the line below on this page to select it:
Right-click or control -click the line and select
Services ▹ Reveal in Finder (or just Reveal )
from the contextual menu.* A folder should open with a file selected. Drag the file onto the TextEdit icon in the Dock or in the Applications folder to open it. Post the text in the window that opens.
*If you don’t see the contextual menu item, copy the selected text to the Clipboard by pressing the key combination command-C . In the Finder, select
Go ▹ Go to Folder.
from the menu bar and paste into the box that opens by pressing command-V . You may not see what you pasted because a line break is included. Press return .
Oct 14, 2015 8:32 AM
This is what rootless.conf contains:
| /Applications/App Store.app | |
| /Applications/Automator.app | |
| /Applications/Calculator.app | |
| /Applications/Calendar.app | |
| /Applications/Chess.app | |
| /Applications/Contacts.app | |
| /Applications/Dashboard.app | |
| /Applications/Dictionary.app | |
| /Applications/DVD Player.app | |
| /Applications/FaceTime.app | |
| /Applications/Font Book.app | |
| /Applications/Game Center.app | |
| /Applications/Image Capture.app | |
| /Applications/Launchpad.app | |
| /Applications/Mail.app | |
| /Applications/Maps.app | |
| /Applications/Messages.app | |
| /Applications/Mission Control.app | |
| /Applications/Notes.app | |
| /Applications/Photo Booth.app | |
| /Applications/Photos.app | |
| /Applications/Preview.app | |
| /Applications/QuickTime Player.app | |
| /Applications/Reminders.app | |
| /Applications/Safari.app | |
| /Applications/Stickies.app | |
| /Applications/System Preferences.app | |
| /Applications/TextEdit.app | |
| /Applications/Time Machine.app | |
| /Applications/Utilities/Activity Monitor.app | |
| /Applications/Utilities/AirPort Utility.app | |
| /Applications/Utilities/Audio MIDI Setup.app | |
| /Applications/Utilities/Bluetooth File Exchange.app | |
| /Applications/Utilities/Boot Camp Assistant.app | |
| /Applications/Utilities/ColorSync Utility.app | |
| /Applications/Utilities/Console.app | |
| /Applications/Utilities/Digital Color Meter.app | |
| /Applications/Utilities/Disk Utility.app | |
| /Applications/Utilities/Feedback Assistant.app | |
| /Applications/Utilities/Grab.app | |
| /Applications/Utilities/Grapher.app | |
| /Applications/Utilities/Keychain Access.app | |
| /Applications/Utilities/Migration Assistant.app | |
| /Applications/Utilities/Script Editor.app | |
| /Applications/Utilities/System Information.app | |
| /Applications/Utilities/Terminal.app | |
| /Applications/Utilities/VoiceOver Utility.app | |
| /Library/Preferences/SystemConfiguration/com.apple.Boot.plist | |
| /System | |
| * | /System/Library/Caches |
| booter | /System/Library/CoreServices |
| * | /System/Library/CoreServices/Photo Library Migration Utility.app |
| /System/Library/CoreServices/RawCamera.bundle | |
| * | /System/Library/Extensions |
| /System/Library/Extensions/* | |
| UpdateSettings | /System/Library/LaunchDaemons/com.apple.UpdateSettings.plist |
| * | /System/Library/Speech |
| * | /System/Library/User Template |
| /bin | |
| dyld | /private/var/db/dyld |
| /sbin | |
| /usr | |
| * | /usr/libexec/cups |
| * | /usr/local |
| * | /usr/share/man |
| /etc |
| /tmp |
| /var |
Oct 14, 2015 8:38 AM
That’s what it should be, but something else is wrong. Do you have an external storage device you can boot from?
Oct 14, 2015 8:54 AM
Yes, I have an external disk on which I clone/backup the MacBookAir main drive.
I guess this might not be useful, since it is a clone. and thus it will likely have the same issue.
What about booting from the recovery partition of from a USB key?
If needed, I might try to install elcapitan on an external drive and boot from it. What I should then look for?
Thanks a lot. I was afraid this was not an easy issue to solve.
Oct 14, 2015 9:09 AM
Boot from the external drive. Navigate in the Finder to the System folder at the top level of the internal drive—not the one you’re booted from. Inside it is a subfolder named «Library.» Inside that is a subfolder named «Caches.» Drag the Caches folder to the Trash and empty. Then start from the internal drive as usual. The Caches folder should be recreated automatically, hopefully without the corruption it has now.
Oct 14, 2015 9:53 AM
I did that. Booted from an external drive, deleted the Caches subfolder in System/Library on the internal main drive (trash, empty trash).
I rebooted from the main drive.
The os recreated the caches folder, and within that folder now I have only 2 folders:
back to Console, system log. I keep getting over and over:
14/10/2015 23:24:45.000 kernel[0]: Sandbox: coresymbolicatio(1082) System Policy: deny(1) file-write-create /System/Library/Caches/com.apple.coresymbolicationd
14/10/2015 23:24:45.244 coresymbolicationd[1082]: /System/Library/Caches/com.apple.coresymbolicationd/data does not exist, resetting cache
14/10/2015 23:24:45.244 coresymbolicationd[1082]: Attempt to create [/System/Library/Caches/com.apple.coresymbolicationd/data] failed. No such file or directory
14/10/2015 23:24:45.244 coresymbolicationd[1082]: Unable to open storage at /System/Library/Caches/com.apple.coresymbolicationd/data
14/10/2015 23:24:45.246 com.apple.xpc.launchd[1]: (com.apple.coresymbolicationd) Service only ran for 0 seconds. Pushing respawn out by 10 seconds.
Who the **** is trying to write this com.apple.coresymbolicationds fine in that /System/Library/Caches directory.
I am just getting crazy about it!
Thanks a lot for your help and support! 🙂
Источник
9GB com.apple.coresymbolicationd file in Caches
I’m trying to free up disk space, and I came across this:
I’ve read reports of a 600M file, or a 1GB file but never something like this.
Is it safe to delete or does rebooting frequently help clear some of these files?
4 Answers 4
Using things from this link (http://www.macobserver.com/tmo/article/how_to_recover_missing_hard_drive_space/) I found a file — com.apple.coresymbolicationd of 133GB.
To delete, boot in Safe Mode (Cmd-S before the Apple logo comes up), run a filesystem check, mount the drive and then just sudo rm the file
No. Rebooting doesn’t clear cache files in system. You would need to dig into exactly which subsystem creates here caches and determine of there is a way to manually flush them or move them to trash and then reboot to see when/how/what size they get recreated.
I would boot to single user mode and use rm to clear that file since nothing is using it then. You could also use sudo mv /System/Library/Caches/com.apple.coresymbolicationd/data /tmp and then reboot. After the reboot you can delete the file from /tmp with sudo rm /tmp/data .
My hunch is you have Xcode installed and have introduced a large number of symbols into your database from one or more iOS versions so that Xcode can symbolicate crash dumps to assist in debugging apps using Xcode. However, it could also be a bug and whenever that subsystem starts recycling the cache, it will clear itself. If you can limit the number of SDK you use in Xcode, that might help as well. My feeling is the people with 60m files don’t use Xcode, those with 1MB developer for one version of iOS at a time and those with larger size databases have multiple OS X and iOS SDK activated from within Xcode.
Источник
