Every minute two of our Macbook Pro's crash. On my logs I see :
Thread 7 Crashed:
0 libsystem_c.dylib 0x00007fff970db541 __xvprintf + 106
sometimes it's thread 7 and other times :
Thread 10 Crashed:
0 libsystem_c.dylib 0x00007fff970db541 __xvprintf + 106
The full log can be seen here : https://dl.dropboxusercontent.com/u/22331148/Personal/crash_log.txt
I am running OS X Mavericks
Goto to your Google Drive preferences
UNCHECK "show file sync status icons and right click menu"
Solved the issue for me.
Related
While checking Xcode 8.2 changes I found that now we can record simulator using Terminal.
So I am trying to record video from iOS simulator as describe in this Apple Document.
Taking a Screenshot or Recording a Video Using the Command Line
Command:
xcrun simctl io booted recordVideo demoVideo.mp4
Error:
2016-12-20 15:44:27.206 simctl[6434:984477] *** Assertion failure in +[SimDisplayVideoWriter videoWriter], /BuildRoot/Library/Caches/com.apple.xbs/Sources/CoreSimulator/CoreSimulator-338.16/SimulatorKit/SimDisplayVideoWriter.m:48
2016-12-20 15:44:27.207 simctl[6434:984477] *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Failed to create metal device for video writer.'
*** First throw call stack:
(
0 CoreFoundation 0x00007fffa07f90db __exceptionPreprocess + 171
1 libobjc.A.dylib 0x00007fffb548ba2a objc_exception_throw + 48
2 CoreFoundation 0x00007fffa07fdc32 +[NSException raise:format:arguments:] + 98
3 Foundation 0x00007fffa2266d50 -[NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 195
4 SimulatorKit 0x000000010a248c53 +[SimDisplayVideoWriter videoWriter] + 1015
5 SimulatorKit 0x000000010a2499e5 +[SimDisplayVideoWriter videoWriterForURL:fileType:] + 316
6 simctl 0x000000010a168a00 simctl + 31232
7 simctl 0x000000010a166bee simctl + 23534
8 simctl 0x000000010a170d52 simctl + 64850
9 libdispatch.dylib 0x00007fffb5d3fef7 _dispatch_call_block_and_release + 12
10 libdispatch.dylib 0x00007fffb5d370b8 _dispatch_client_callout + 8
11 libdispatch.dylib 0x00007fffb5d39029 _dispatch_root_queue_drain + 917
12 libdispatch.dylib 0x00007fffb5d38c47 _dispatch_worker_thread3 + 99
13 libsystem_pthread.dylib 0x00007fffb5f84712 _pthread_wqthread + 1299
14 libsystem_pthread.dylib 0x00007fffb5f841ed start_wqthread + 13
)
libc++abi.dylib: terminating with uncaught exception of type NSException
Abort trap: 6
iOS simulator and application both working properly. This error only shown in Terminal.
I am using Xcode 8.2. Tried in Simulator of iPhone 7, 7 Plus, SE with iOS 10.2.
Am I missing any detail or need to install and component?
Video recording is only supported on Macs that support Metal. If your system doesn't support metal, you will see an abort with that message. Yeah, we should make that error message more user friendly.
To see a list of supported systems, you can check out https://support.apple.com/en-us/HT205073
this was also fixed in Xcode 8.3 Beta: http://adcdownload.apple.com/Developer_Tools/Xcode_8.3_beta/Release_Notes_for_Xcode_8.3_beta.pdf
• Videos recorded by the simctl tool of the xcrun command line tool now support scrubbing and import into video editors correctly. (29654098)
I did not test this currently but it is quite possible that in stable version of Xcode this bug will be fixed
I have a problem with my Vagrant VM running on VirtualBox: every time I close the lid of my MacBook, the VM is aborted and I have to 'vagrant up' it again. I don't think it's the intended behaviour, and it's quite annoying to start over every time.
Checking the DiagnosticReports folder I can find a crash report from VirtualBox every time I close the lid with a running VM, this is an extract from the first part:
Process: VBoxHeadless [6267]
Path: /Applications/VirtualBox.app/Contents/MacOS/VBoxHeadless
Identifier: VBoxHeadless
Version: ???
Code Type: X86-64 (Native)
Parent Process: VBoxSVC [6215]
Responsible: VirtualBox [6210]
User ID: 501
Date/Time: 2015-02-15 10:27:16.982 +0100
OS Version: Mac OS X 10.10.2 (14C109)
Report Version: 11
Anonymous UUID: 453DE236-2C46-1B97-1C8F-D91BAF75710E
Sleep/Wake UUID: 21FE4DBC-7544-453E-B166-C48801F5CDDB
Time Awake Since Boot: 35000 seconds
Time Since Wake: 2700 seconds
Crashed Thread: 7 EMT
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
VM Regions Near 0:
-->
__TEXT 0000000100000000-0000000100008000 [ 32K] r-x/rwx SM=COW /Applications/VirtualBox.app/Contents/MacOS/VBoxHeadless
Thread 0:: Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x00007fff8bf734de mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff8bf7264f mach_msg + 55
2 com.apple.CoreFoundation 0x00007fff8b356b34 __CFRunLoopServiceMachPort + 212
3 com.apple.CoreFoundation 0x00007fff8b355ffb __CFRunLoopRun + 1371
4 com.apple.CoreFoundation 0x00007fff8b355858 CFRunLoopRunSpecific + 296
5 VBoxHeadless.dylib 0x0000000100080b91 TrustedMain + 44177
6 VBoxHeadless.dylib 0x0000000100080e5b TrustedMain + 44891
7 VBoxHeadless.dylib 0x0000000100079b31 TrustedMain + 15409
8 VBoxHeadless 0x0000000100003d95 start + 7061
9 VBoxHeadless 0x0000000100002234 start + 52
Is there anything I can do to fix this thing by myself, or do I have to open a bug report for the VirtualBox support team?
OSX v10.10.2
VirtualBox v4.3.22
Vagrant v1.7.2
This bug has been report to Oracle Virtualbox.
And the bug has just been fixed and released in Virtualbox 4.3.24. You can download the latest version (VirtualBox-4.3.24-98716-OSX.dmg) from https://www.virtualbox.org/wiki/Downloads.
As chaserx pointed out, it's a matter of version.
Reverting to VirtualBox v4.3.20 solved the problem, for the moment...
If anyone is having this problem on Ubuntu, adding following lines to /etc/NetworkManager/NetworkManager.conf and restarting service with sudo service network-manager restart solved the problem for me:
[keyfile]
unmanaged-devices=interface-name:vboxnet0
Source: https://www.virtualbox.org/ticket/13873#comment:16
VirtualBox Manager 5.0.8
Network Manager 1.0.4-0ubuntu5
I tried to run the phonon example code, Music player Example, came with the sdk. It runs well on Windows, but crashes while starting on Mac OS Snow Leopard 10.6.8. This is the crash details:
crash line:
audioOutput = new Phonon::AudioOutput(Phonon::MusicCategory, this);
crash log and call stack:
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0×0000000000000008
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Thread 0 Crashed: Dispatch queue: com.apple.main-thread
0 QtCore 0×0000000100e9c8f2 QObject::moveToThread(QThread*) + 34
1 QtDBus 0×00000001010b4912 _q_sessionBus() + 162
2 QtDBus 0×00000001010b4a71 QDBusConnection::sessionBus() + 17
3 phonon 0×000000010001beab Phonon::FactoryPrivate::FactoryPrivate() + 219
4 phonon 0×000000010001edc2 Phonon::Factory::registerFrontendObject(Phonon::MediaNodePrivate*) + 146
5 phonon 0×0000000100028f92 Phonon::MediaNodePrivate::MediaNodePrivate(Phonon::MediaNodePrivate::CastId) + 82
6 phonon 0×00000001000137bf Phonon::AudioOutput::AudioOutput(Phonon::Category, QObject*) + 63
7 com.yourcompany.qmusicplayer 0×00000001000026cc MainWindow::MainWindow() + 108
8 com.yourcompany.qmusicplayer 0×00000001000024a2 main + 114
9 com.yourcompany.qmusicplayer 0×0000000100002404 start + 52
I believe that this was a problem with Qt 4.8.0. It required dbus to be installed on your machine. There are workarounds like installing dbus on your machine or rebuilding Qt with a patch, but I believe it's fixed in Qt 4.8.1 so probably just use that.
I am trying to build NPAPI plugin for safari and have been trying to run the simple NPAPI plugin example from https://github.com/mikma/npsimple on Safari on Mac.
The plugin can use npapi library from WEBKIT_DARWIN_SDK or from XULRUNNER_SDK (downloaded from mozilla.org for mac os).
The plugin works as expected by using WEBKIT_DARWIN_SDK but since it conflicts with my other libraries I can't use it. Now the only way left is to use XULRUNNER_SDK but using that results in a crash on NP_Initialize. Since this is the most basic application using NPAPI it is expected to work ( everything is same expect the fact that internal implementation of webkit and xulrunner could be different).
Am I missing something here?
Pasting initial few lines from the log
Thread 0 Crashed: Dispatch queue: com.apple.main-thread
0 net.webvm 0x00000001004f8228 NP_GetEntryPoints + 24
1 net.webvm 0x00000001004f82b3 NP_Initialize + 67
2 com.apple.WebKit.PluginHost 0x00000001cfb65188 0x1cfb52000 + 78216
3 com.apple.WebKit.PluginHost 0x00000001cfb599e1 0x1cfb52000 + 31201
4 com.apple.WebKit.PluginHost 0x00000001cfb54ad3 0x1cfb52000 + 10963
5 com.apple.CoreFoundation 0x00007fff84fe9a49 __CFRunLoopDoBlocks + 297
6 com.apple.CoreFoundation 0x00007fff84fabe76 __CFRunLoopRun +
You might want to try starting from the npapi-sdk Mac example, which is both simpler than npsimple and more up to date.
For iOS crash reports, it is sufficient to drag and drop the crash report to the Organizer.
Symbolicating iPhone App Crash Reports
But this method doesn't work for Mac OSX crash reports.
How can I symbolicate my Mac OSX crash report ?
Thanks !!
You can use the atos command to get the line number where the app crashed.
Heres a quick guide:
Create a directory for your working files
Open Xcode, select Window->Organizer, goto the Archive tab and find the version of your app that experienced the crash.
Right click on the app archive and select "Show in Finder"
Right click on the .xarchive, select "Show Contents" and find the AppName.dSYM directory and the app and copy them to your working folder
Copy the stack trace to your working folder
Open terminal and change to your working folder. An ls should show YourApp.app YourApp.app.dSYM stacktrace.txt
Open your stack trace in TextEdit. Your going to need to find the Code Type from the header (system architecture - eg. X86-64) and the addresses of the crash. Search through the threads to find the one that crashed (it will say something like "Thread 2 Crashed") then find your objects. You need the two addresses (hex numbers) from that line to get the code line.
Once you've got all the information you need to run the following in the terminal:
atos -o YourApp.app/Contents/MacOS/YourApp -arch x86_64 -l [load-address] [address]
For example, heres an extract from a stacktrace:
Process: MyApp [228]
Path: /Applications/MyApp.app/Contents/MacOS/MyApp
Identifier: uk.co.company.app
Version: 1.0 (1)
App Item ID: 774943227
App External ID: 218062633
Code Type: X86-64 (Native)
Parent Process: launchd [154]
Responsible: MyApp [228]
User ID: 501
Date/Time: 2013-12-17 10:20:45.816 +0100
OS Version: Mac OS X 10.9 (13A603)
Report Version: 11
Anonymous UUID: 7AA662B1-7696-A2C5-AF56-9D4BA2CE9515
Crashed Thread: 2
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
<snip>
Thread 2 Crashed:
0 libsystem_kernel.dylib 0x00007fff8b95a866 __pthread_kill + 10
1 libsystem_pthread.dylib 0x00007fff8bf4f35c pthread_kill + 92
2 libsystem_c.dylib 0x00007fff87571bba abort + 125
3 libsystem_malloc.dylib 0x00007fff897ae093 free + 411
4 uk.co.company.app 0x0000000103580606 0x10356e000 + 75270
5 uk.co.company.app 0x00000001035803da 0x10356e000 + 74714
6 com.apple.Foundation 0x00007fff8d00970b __NSThread__main__ + 1318
7 libsystem_pthread.dylib 0x00007fff8bf4e899 _pthread_body + 138
8 libsystem_pthread.dylib 0x00007fff8bf4e72a _pthread_start + 137
9 libsystem_pthread.dylib 0x00007fff8bf52fc9 thread_start + 13
I can see that the "Code Type" is x86_64, that Thread 2 crashed, and that on line 4 my code was running so we have the addresses we need. Using this information I run the following:
$ atos -o MyApp.app/Contents/MacOS/MyApp -arch x86_64 -l 0x10356e000 0x0000000103580606
This returns:
got symbolicator for MyApp.app/Contents/MacOS/MyApp, base address 100000000
obj_free (in MyApp) (somefile.c:135)
Telling me my app crashed at line 135 of somefile.c
#inkjet 's comment above deserves its own answer.
He built an app that does a full symbolication from your dsym and .crash file.
A free alternative to Sumbolon that I made: bch.us.to/apps/macsymbolicator — It uses atos in the same way described by Rich Able below. – inket Dec 24 '13 at 4:39
putting it all together:
download Mac Symbolicator from here
Open Xcode, select Window->Organizer, goto the Archive tab and find
the version of your app that experienced the crash.
Right click on the app archive and select "Show in Finder"
Right click on the .xarchive, select "Show Contents" and find the
AppName.dSYM directory
Drag your .crash file and AppName.dsym to Sumbolon
Magic happens
this link
this link explains everything to symbolicate the crash log with the line no of crash. you just need to have .dsyms file, .app file and crash log in same folder
i looked around and find nothing better than this. so i am posting it by hoping this will help others.