- Mac Os Library Logs Crashreporter 10
- Mac Os Library Logs Crash Reporter Free
- Mac Os Library Logs Crashreporter Mobiledevice
Sep 25, 2018 How to clear log files on a Mac manually Open Finder and select 'Go to Folder' in the Go menu. Type in /Library/Logs and hit Enter to proceed to this folder (pay attention to the use of “” — this will ensure that you’re cleaning user log files, not the system log files). To find the crash files, you can run Console app which will display all the system messages. If any specific application crashed, look in User Reports. If it's system crash, check in System Reports. Once you have found the crash file, you can Reveal in Finder (usually located in /Library/Logs/DiagnosticReports).
Whenever a program crashes in OS X, you are presented with a small window that indicates the program quit unexpectedly (Apple’s vernacular for “it crashed”). Whenever this happens, first choose the default option in this window to ignore the issue, and then try relaunching your program. However, if it occurs again then you may find some quick answers in the crash report that can be opened by clicking the “Report” button.
When you open this report, you will see a bunch of cryptic-looking details that may seem only useful to a programmer, but with careful review you may spot something that can help you overcome your problem.
Aug 07, 2012 Accessing iOS Crash Logs on a Mac. For Mac OS X: Connect the iPad or iPhone to the Mac and sync it as usual; Hit Command+Shift+G and navigate to /Library/Logs/CrashReporter/MobileDevice/ For those with multiple iOS devices, select the proper device that you want to retrieve the crash log from. Apr 12, 2016 Using the OS X crash reporter to diagnose a program failure Whenever a program crashes in OS X, you are presented with a small window that indicates the program quit unexpectedly (Apple’s vernacular for “it crashed”). The directory /var/mobile/Library/Logs/CrashReporter is the one in your iOS device, instead of your Mac OS X/Windows computer. The directory /Library/Logs/CrashReporter/MobileDevice mentioned.
The main details of a crash report outline information in separate sections about the process, and outline essentially what the system last saw about the program before it was terminated. This includes any open files (executable and otherwise) that the program had open, application-specific information, and execution threads in which the program was running.For the most part all of the details of a crash report can be ignored, but if you look at each of the subsections in whole you are presented with a view of what the system saw when the program crashed. In most cases, you will see a specified point where the program crashed, indicated by a “Thread crashed” or similar content.
The crash reporter alert will show whenever a program has unexpectedly quit.
Unfortunately there is no stereotyped approach to reviewing a crash report that will get you an answer at all times, but by reviewing a case or two you may pick up some approaches that can help you troubleshoot your situation.
In the example here, Apple’s Photos program was crashing every time it was opened. This behavior is common when a configuration for a program is corrupt, or if a corrupted file previously opened by the program is being re-opened on launch.
In looking at the crash report, we can see that “Thread 3” is the process that crashed:
The crash report shows cryptic details about the crashed thread, but you can see some more relevant actions that were taken, listed toward the top (click for larger view).
If you do not know what threads are, programs for your computer are broken down into separate running parts called threads, which in part allow the program to run more modularly and not get hung up on any particular task. For instance, without threading, the act of opening a file would freeze any running program while it waits for user input, but having this file-opening task be in a separate thread means the main program can keep running and wait for the file to be chosen and presented, so nothing has to pause.
Programs can be more stable in this manner as well, since threads experiencing problems can often be restarted instead of taking down the whole program. This being said, often for logical and nuanced programming reasons, back-end features that are core to a program’s functions will run in separate threads, but if any one runs into problems, then they will cause the program to fail.
In looking at the report, it is obvious nothing much can be gleaned from the details about this thread, since it simply references library names and system calls. We simply know that an abort command was called and that the thread has to do with OpenGL (a graphics library). This lets us know the thread had to do with rendering graphical content from Photos.
While the thread report does not show much, scrolling up does show a key to the puzzle. Under the listing of process details we can see Application Specific Information, where an “Assertion failure” entry is listed. An assertion failure to a programmer means some program state that was expected has not occurred, and therefore the program is being forced to quit instead of proceed in a potentially unsafe state. This is good, and indicates the program is in fact behaving according to its coding, despite crashing.
The application-specific details about the crash show a specific cached file that is suspect, indicating the solution here is to clear this cache and allow the program to recreate it (click for larger view).
As with reading thread details, the specifics of an assertion failure may be difficult to diagnose, but in this case we can see an implicated cache file. Caches are just small settings and states that are stored from the last time the program ran, which may be quickly accessed for the program to run more efficiently the next time it loads. This is also good, because it means they are temporary files that are dynamically recreated.
In this case, a misconfiguration of this indicated cache file is all that was the problem, and going to its specific location on disk (Macintosh HD > Library > Caches > com.apple.xbs > Sources > PhotoApp > PhotoApp-370.42 > lib > paimaging > PhotoApps) allows us to remove the cached file so Photos can open again. You can also take a more global approach and delete the parent “com.apple.xbs” file in the Caches folder itself, which will force Photos to recreate all of its cached files.
What are log files and what do they do?
Log files are a journal of system parameters and entries describing everything that takes place on your Mac. Any operation that is being performed at any time is noted down in the form of logs, much like a “black box” on an airplane.
For the most part, logs contain crash reports and app errors. To us, regular users, this information bears no sense because it’s unreadable. But when you need to diagnose a problem, log files are an indispensable invention.
How to delete user log files?
Why would anyone want to delete user logs on Mac? First, deleting outdated logs may speed up some of your apps. Second, however small they are, logs still take space on your disk. And lastly, outdated logs could potentially cause software conflicts.
User logs are a part of your user profile. They are stored at:
~/Library/Logs
You should know that deleting user logs is not an everyday operation. It may backfire if you don’t know what you’re deleting. But since you asked, here is how it’s done.
Mac Os Library Logs Crashreporter 10
We've got two ways to do it: the manual way and the CleanMyMac X way.
How to clear log files on a Mac manually
- Open Finder and select 'Go to Folder' in the Go menu.
- Type in ~/Library/Logs and hit Enter to proceed to this folder (pay attention to the use of “~” — this will ensure that you’re cleaning user log files, not the system log files).
- Optional step: You can highlight & copy everything to a different folder in case anything goes wrong.
- Select all files and press Command+backspace.
- Restart your Mac.
Note: We recommend that you remove the insides of these folders, but not the folders themselves. Also note that some system applications, like Mail, have their own logs stored elsewhere.
Remember, if you want the additional space from cleaning these log files, be sure to empty your Trash. To do this, Control+click on the Trash icon in the dock and select “Empty Trash.”
In addition, some log files can be found in the /var/log folder, but not all the items contained therein are safe to remove. That’s why it is safer to remove log files using a Mac cleaning utility like CleanMyMac X.
How to clear log files with CleanMyMac X
Rather than searching all over your Mac for log files yourself, you can clean up logs with CleanMyMac X in just 4 steps. And that’s not all it does! Anyway, to clean them up with CleanMyMac X:
- Download CleanMyMac X (free version) and launch it.
- Choose System Junkin the left menu.
- Click Scan at the bottom of CleanMyMac X.
- Hit Clean.
Done! If you’d like to remove only log files and nothing else, click on Review Details before clicking Clean. Deselect everything except for System Log Files and User Log Files, and then click Clean.
Make sure that once you have finished clearing out these logs for additional hard drive space, you empty out your Trash. To do this, Control-click on the Trash icon in the dock and select “Empty Trash.” Restart your Mac afterward so your Mac can begin to create new log files.
Is it safe to delete log files?
Mac Os Library Logs Crash Reporter Free
Many experienced users prefer to clean their user logs as part of their Mac cleaning routine on Mac. Though it doesn’t directly translate into speed, there is some benefit in keeping your disk clean. Some apps have notoriously large log files, especially media apps. For example, writing this article I’ve found a single log file by Elmedia player that weighted 325 MB.
Mac Os Library Logs Crashreporter Mobiledevice
As a word of caution, you shouldn’t delete the entire Logs folder, only delete what’s contained inside. As we have said, log files serve for diagnostic purposes. If your Mac is doing well, there’s nothing particularly harmful in deleting logs.
Cleaning up log files with CleanMyMac X is as easy as can be. And, like we said before, it can do so much more, too! With CleanMyMac X, you can clean up outdated apps, language packs, universal binaries, and gigabytes of useless junk you didn’t even know you had. Download CleanMyMac X now and feel what it’s like to have a faster, cleaner Mac.