10.10.3
There is a process performed by root which uses ~350% of the CPU causing my MBP to heat up. When I quit it in the Activity Monitor, it starts straight away.
When I try to analyse it in the Activity Monitor, it simply does not work. It shows the "Doing the Analysis WindoW" but does not proceed.
Any ideas?
MacBook Pro, OS X Yosemite (10.10.3)
It creates crash reports every 5 seconds... Thats the report from the console. Its something with the locationnd I guess.
I tried to acces "Privacy and Security" from the "Preferences Panel" but it keeps on crashing on me. I even tried in safe mode, but it crashed. PRAM reset did not help neither. Any ideas?!
Process: locationd [868]
Path: /usr/libexec/locationd
Identifier: locationd
Version: 1615.24
Code Type: X86-64 (Native)
Parent Process: launchd [1]
Responsible: locationd [868]
User ID: 205
PlugIn Path: /usr/libexec/locationd
PlugIn Identifier: locationd
PlugIn Version: ??? (1615.24)
Date/Time: 2015-06-01 16:18:18.530 +0200
OS Version: Mac OS X 10.10.3 (14D136)
Report Version: 11
Anonymous UUID: ...
Time Awake Since Boot: 300 seconds
Crashed Thread: 0
Exception Type: EXC_BAD_ACCESS (Code Signature Invalid)
Exception Codes: 0x0000000000000032, 0x0000000108eeb000
kernel messages:
-0 sec CODE SIGNING: cs_invalid_page(0x108eeb000): p=868[locationd] final status 0x3004a00, denying page sending SIGKILL
-0 sec CODE SIGNING: process 868[locationd]: rejecting invalid page at address 0x108eeb000 from offset 0x48f000 in file "/usr/libexec/locationd" (cs_mtime:1419277632.0 == mtime:1419277632.0) (signed:1 validated:1 tainted:1 wpmapped:0 slid:0)
-3 sec CODE SIGNING: cs_invalid_page(0x10db49000): p=865[locationd] final status 0x3004a00, denying page sending SIGKILL
-3 sec CODE SIGNING: process 865[locationd]: rejecting invalid page at address 0x10db49000 from offset 0x48f000 in file "/usr/libexec/locationd" (cs_mtime:1419277632.0 == mtime:1419277632.0) (signed:1 validated:1 tainted:1 wpmapped:0 slid:0)
-7 sec CODE SIGNING: cs_invalid_page(0x1097bc000): p=862[locationd] final status 0x3004a00, denying page sending SIGKILL
-7 sec CODE SIGNING: process 862[locationd]: rejecting invalid page at address 0x1097bc000 from offset 0x48f000 in file "/usr/libexec/locationd" (cs_mtime:1419277632.0 == mtime:1419277632.0) (signed:1 validated:1 tainted:1 wpmapped:0 slid:0)
-10 sec CODE SIGNING: cs_invalid_page(0x10c4e6000): p=860[locationd] final status 0x3004a00, denying page sending SIGKILL
-10 sec CODE SIGNING: process 860[locationd]: rejecting invalid page at address 0x10c4e6000 from offset 0x48f000 in file "/usr/libexec/locationd" (cs_mtime:1419277632.0 == mtime:1419277632.0) (signed:1 validated:1 tainted:1 wpmapped:0 slid:0)
-14 sec CODE SIGNING: cs_invalid_page(0x108e78000): p=858[locationd] final status 0x3004a00, denying page sending SIGKILL
-14 sec CODE SIGNING: process 858[locationd]: rejecting invalid page at address 0x108e78000 from offset 0x48f000 in file "/usr/libexec/locationd" (cs_mtime:1419277632.0 == mtime:1419277632.0) (signed:1 validated:1 tainted:1 wpmapped:0 slid:0)
VM Regions Near 0x108eeb000:
__DATA 0000000108ee3000-0000000108eeb000 [ 32K] rw-/rwx SM=NUL /usr/libexec/locationd
--> __LINKEDIT 0000000108eeb000-0000000108f0c000 [ 132K] r--/rwx SM=COW /usr/libexec/locationd
__LINKEDIT 0000000108f0c000-0000000108f0d000 [ 4K] r--/rwx SM=NUL /usr/libexec/locationd
Application Specific Information:
dyld: launch, loading dependent libraries
/usr/libexec/locationd
Thread 0 Crashed:
0 dyld 0x00007fff6cbc811d ImageLoaderMachOCompressed::rebase(ImageLoader::LinkContext const&) + 205
1 dyld 0x00007fff6cbbff94 ImageLoader::recursiveRebase(ImageLoader::LinkContext const&) + 126
2 dyld 0x00007fff6cbbf70c ImageLoader::link(ImageLoader::LinkContext const&, bool, bool, bool, ImageLoader::RPathChain const&) + 144
3 dyld 0x00007fff6cbb5be4 dyld::link(ImageLoader*, bool, bool, ImageLoader::RPathChain const&) + 166
4 dyld 0x00007fff6cbb6a87 dyld::_main(macho_header const*, unsigned long, int, char const**, char const**, char const**, unsigned long*) + 2370
5 dyld 0x00007fff6cbb2276 dyldbootstrap::start(macho_header const*, int, char const**, long, macho_header const*, unsigned long*) + 512
6 dyld 0x00007fff6cbb2036 _dyld_start + 54
Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x0000000108eed380 rbx: 0x0000000000000000 rcx: 0x0000000108a54000 rdx: 0x0000000000000000
rdi: 0x0000000108eed380 rsi: 0x0000000108eed380 rbp: 0x00007fff571ab310 rsp: 0x00007fff571ab260
r8: 0x0000000108eeb000 r9: 0x0000000108a54000 r10: 0x0000000108eed380 r11: 0x0000000108eed380
r12: 0x0000000108eeb000 r13: 0x00007fff6cbef3d8 r14: 0x0000000008a54000 r15: 0x00007fff6cbdbb17
rip: 0x00007fff6cbc811d rfl: 0x0000000000010246 cr2: 0x0000000108eeb000
Logical CPU: 2
Error Code: 0x00000004
Trap Number: 14
External Modification Summary:
Calls made by other processes targeting this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by all processes on this machine:
task_for_pid: 3541
thread_create: 0
thread_set_state: 0
VM Region Summary:
ReadOnly portion of Libraries: Total=99.4M resident=84.7M(85%) swapped_out_or_unallocated=14.6M(15%)
Writable regions: Total=12.4M written=2612K(21%) resident=3784K(30%) swapped_out=0K(0%) unallocated=8864K(70%)
REGION TYPE VIRTUAL
=========== =======
STACK GUARD 56.0M
Stack 8192K
VM_ALLOCATE 8K
__DATA 7732K
__LINKEDIT 20.1M
__TEXT 79.4M
__UNICODE 552K
shared memory 4K
=========== =======
TOTAL 171.6M
I cannot access Private Setting in the preferences window. It crashes. Even when I start in safe mode. PRAM reset did not help neither.
Restart the computer in safe mode. Certain caches maintained by the system will be rebuilt.
Safe mode is much slower to start up than normal. The next normal startup may also be somewhat slow.
When the login screen appears, restart as usual (not in safe mode) and test. There's no need to log in while in safe mode.
Note: If FileVault is enabled in OS X 10.9 or earlier, or if a firmware password is set, or if the startup volume is a software RAID, you can’t start in safe mode. In that case, ask for instructions.
See below if there's no change.
If you don't already have a current backup, back up all data, then reinstall the OS.* You don't need to erase the startup volume, and you won't need the backup unless something goes wrong. If the system was upgraded from an older version of OS X, you may need the Apple ID and password you used.
There are ways to back up a computer that isn't fully functional. Ask if you need guidance.
If you installed the Java runtime distributed by Apple and still need it, you'll have to reinstall it. The same goes for Xcode. All other data will be preserved.
*The linked support article refers to OS X 10.10 ("Yosemite"), but the procedure is the same for OS X 10.7 ("Lion") and later.
That did not help. PRAM reset neither.
I installed this update OS X Yosemite 10.10.3 Combo Update instead of completely reinsallting the system and that worked! The Report Crash is gone 🙂
Report Crash ~350% of CPU Yosemite
