Mac overheating after upgrade to Catalina - constant crash reports

I was running Mojave. MacBook Pro, mid 2012, 2.5 GHz Dual-Core i5, 16GB 1600 Mhz DDR3. I restarted it and the Chrome icon had a question mark after it booted up. I tried installing chrome a few times but got a message that Safari could not continue as the dmg file was not valid. I decided to upgrade to Catalina in case the Mojave was too old for Google. After I updated, my MacBook Pro started running really hot. Something called "Crash Report" was using the CPU continuously. I called Apple. The suggestion was to reinstall Catalina and see if the problem persisted. By this time the Chrome icon had disappeared from the dock and was replaced by a bigger question mark.


After the second install of Catalina the laptop is still really hot, too hot on the bottom to leave my hands there. In fact I don't even want to use it in case the high temperature damages the computer somehow.


Etrecheck says there is excessive CPU usage.


Here are the last few lines of the system log that keeps generating every few seconds.


Sep 10 21:33:14 Chriss-MBP-2 com.apple.xpc.launchd[1] (com.apple.xpc.launchd.domain.pid.locationd.4047): Failed to bootstrap path: path = /usr/libexec/locationd, error = 108: Invalid path

Sep 10 21:33:17 Chriss-MBP-2 com.apple.xpc.launchd[1] (com.apple.locationd[4047]): Service exited due to SIGSEGV | sent by exc handler[4047]

Sep 10 21:33:17 Chriss-MBP-2 com.apple.xpc.launchd[1] (com.apple.xpc.launchd.domain.pid.locationd.4048): Failed to bootstrap path: path = /usr/libexec/locationd, error = 108: Invalid path

Sep 10 21:33:20 Chriss-MBP-2 com.apple.xpc.launchd[1] (com.apple.locationd[4048]): Service exited due to SIGSEGV | sent by exc handler[4048]

Sep 10 21:33:21 Chriss-MBP-2 com.apple.xpc.launchd[1] (com.apple.xpc.launchd.domain.pid.locationd.4049): Failed to bootstrap path: path = /usr/libexec/locationd, error = 108: Invalid path

Sep 10 21:33:23 Chriss-MBP-2 com.apple.xpc.launchd[1] (com.apple.locationd[4049]): Service exited due to SIGSEGV | sent by exc handler[4049]

Sep 10 21:33:24 Chriss-MBP-2 com.apple.xpc.launchd[1] (com.apple.xpc.launchd.domain.pid.locationd.4050): Failed to bootstrap path: path = /usr/libexec/locationd, error = 108: Invalid path

Sep 10 21:33:27 Chriss-MBP-2 com.apple.xpc.launchd[1] (com.apple.locationd[4050]): Service exited due to SIGSEGV | sent by exc handler[4050]


When I called Apple back, they said I should take the computer to a third party for cleaning because it sounded like a dust build up.


Any ideas about how the dust is causing all the continuous action?



MacBook Pro 15″, macOS 10.14

Posted on Sep 10, 2023 7:36 PM

Reply
1 reply

Sep 13, 2023 8:51 AM in response to cbgrus

cbgrus wrote:

I was running Mojave. MacBook Pro, mid 2012, 2.5 GHz Dual-Core i5, 16GB 1600 Mhz DDR3. I restarted it and the Chrome icon had a question mark after it booted up. I

tried installing chrome a few times but got a message that Safari could not continue as the dmg file was not valid. I decided to upgrade to Catalina in case the Mojave was too old for Google. After I updated, my MacBook Pro started running really hot. Something called "Crash Report" was using the CPU continuously.

I called Apple. The suggestion was to reinstall Catalina and see if the problem persisted. By this time the Chrome icon had disappeared from the dock and was replaced by a bigger question mark.

After the second install of Catalina the laptop is still really hot, too hot on the bottom to leave my hands there. In fact I don't even want to use it in case the high temperature damages the computer somehow.

Etrecheck says there is excessive CPU usage.

Here are the last few lines of the system log that keeps generating every few seconds.

Sep 10 21:33:14 Chriss-MBP-2 com.apple.xpc.launchd[1] (com.apple.xpc.launchd.domain.pid.locationd.4047): Failed to bootstrap path: path = /usr/libexec/locationd, error = 108: Invalid path

Sep 10 21:33:27 Chriss-MBP-2 com.apple.xpc.launchd[1] (com.apple.locationd[4050]): Service exited due to SIGSEGV | sent by exc handler[4050]



posting the Etrecheck report would be more insightful...

If you need help interpreting the report you can post it here in its entirety in the "Additional Text" box in the editing toolbar below, in your reply.




< Service exited due to SIGSEGV >

A crash due to a memory access issue occurs when an app uses memory in an unexpected way.



Google is a search engine, Chrome is a browser


The latest Chrome may not be compatible with the older macOS Mojave. or Catalina..

Try a different third party browser(?) and compare your results

Mac overheating after upgrade to Catalina - constant crash reports

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