Apple Event: May 7th at 7 am PT

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

console help needed interpreting these messages on system.log

The message below keeps appearing in system log. I don't know if it means that there's a bug in my system or what. I was able to pin down the file for VTDecoderXPCService but I don't know if I should delete it or not. Does anyone know what this line of code means?


eb 12 12:53:32 Lucys-MacBook-Pro efilogin-helper[8907]: objc[8907]: Class EFILWLogging is implemented in both /System/Library/PrivateFrameworks/EFILogin.framework/Versions/A/EFILogin (0x7fff89a3b510) and /System/Library/PrivateFrameworks/EFILogin.framework/Versions/A/Resources/EFIResourceBuilder.bundle/Contents/MacOS/EFIResourceBuilder (0x101c42080). One of the two will be used. Which one is undefined.

Feb 12 12:53:33 Lucys-MacBook-Pro VTDecoderXPCService[8909]: DEPRECATED USE in libdispatch client: Changing the target of a source after it has been activated; set a breakpoint on _dispatch_bug_deprecated to debug

Feb 12 12:53:33 Lucys-MacBook-Pro VTDecoderXPCService[8909]: DEPRECATED USE in libdispatch client: Changing target queue hierarchy after xpc connection was activated; set a breakpoint on _dispatch_bug_deprecated to debug

Feb 12 12:53:33 Lucys-MacBook-Pro VTDecoderXPCService[8909]: DEPRECATED USE in libdispatch client: Changing the target of a source after it has been activated; set a breakpoint on _dispatch_bug_deprecated to debug

Feb 12 12:53:33 Lucys-MacBook-Pro VTDecoderXPCService[8909]: DEPRECATED USE in libdispatch client: Changing target queue hierarchy after xpc connection was activated; set a breakpoint on _dispatch_bug_deprecated to debug

Feb 12 12:53:37 Lucys-MacBook-Pro ReportCrash[8913]: objc[8913]: Class CrashReport is implemented in both /System/Library/PrivateFrameworks/CrashReporterSupport.framework/Versions/A/CrashReporterSupport and /System/Library/CoreServices/ReportCrash. One of the two will be used. Which one is undefined.

Feb 12 12:53:43 Lucys-MacBook-Pro efilogin-helper[8917]: objc[8917]: Class EFILWLogging is implemented in both /System/Library/PrivateFrameworks/EFILogin.framework/Versions/A/EFILogin and /System/Library/PrivateFrameworks/EFILogin.framework/Versions/A/Resources/efilogin-helper. One of the two will be used. Which one is undefined.

Feb 12 12:53:43 Lucys-MacBook-Pro efilogin-helper[8917]: objc[8917]: Class EFILWLogging is implemented in both /System/Library/PrivateFrameworks/EFILogin.framework/Versions/A/EFILogin (0x7fff89a3b510) and /System/Library/PrivateFrameworks/EFILogin.framework/Versions/A/Resources/EFIResourceBuilder.bundle/Contents/MacOS/EFIResourceBuilder (0x101e94080). One of the two will be used. Which one is undefined.

Feb 12 12:53:44 Lucys-MacBook-Pro VTDecoderXPCService[8918]: DEPRECATED USE in libdispatch client: Changing the target of a source after it has been activated; set a breakpoint on _dispatch_bug_deprecated to debug

Feb 12 12:53:44 Lucys-MacBook-Pro VTDecoderXPCService[8918]: DEPRECATED USE in libdispatch client: Changing target queue hierarchy after xpc connection was activated; set a breakpoint on _dispatch_bug_deprecated to debug

Feb 12 12:53:44 Lucys-MacBook-Pro VTDecoderXPCService[8918]: DEPRECATED USE in libdispatch client: Changing the target of a source after it has been activated; set a breakpoint on _dispatch_bug_deprecated to debug

Feb 12 12:53:44 Lucys-MacBook-Pro VTDecoderXPCService[8918]: DEPRECATED USE in libdispatch client: Changing target queue hierarchy after xpc connection was activated; set a breakpoint on _dispatch_bug_deprecated to debug

Feb 12 12:53:56 Lucys-MacBook-Pro com.apple.xpc.launchd[1] (com.apple.mdworker.shared.08000000-0500-0000-0000-000000000000[8905]): Service exited due to SIGKILL | sent by mds[97]


Posted on Feb 12, 2021 2:26 PM

Reply

Similar questions

5 replies

Feb 12, 2021 3:22 PM in response to luzfromberkeley

luzfromberkeley wrote:

I really don't understand


Logs are quite bad at this particular why-is-this-Mac-slow usage.


Download and enable full device access for and run EtreCheck, use the sharing option to copy the report, then open a new reply here and then press the button that looks like a printed page to open a text input box big enough to paste here, amd paste the hardware and software configuration report here.



With the EtreCheck data, we can know more about the hardware and software in use, and what might be causing this Mac to be slow.


If you do not have a current and complete backup, go get a backup now. This on the possibility that there’s a hardware problem arising here.

console help needed interpreting these messages on system.log

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.