Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.sys.mac.apps > #31173

Re: Starting up Messsages app freezes and hogs CPU.

Cross-posted to 2 groups.

Show key headers only | View raw

On 2015-08-21, Ant <ANTant@zimage.com> wrote:
> In comp.sys.mac.comm Jolly Roger <jollyroger@pobox.com> wrote:
>> On 2015-08-20, Ant <ANTant@zimage.com> wrote:
>> > Hi.
>> >
>> > My several days old updated Mac OS X v10.10.5's Messages no longer 
>> > launches. It freezes with a spinning pinwheel ball. Terminal's top -u 
>> > command shows Messages hogging CPU. I tried rebooting Mac OS X, and it 
>> > did not help. I tried renaming my ~/user name/Library/Messages and 
>> > relaunching Messages app, but it said rebuilding database that goes 
>> > forever (no CPU usage this time).  It was working earlier today and 
>> > yesterday.
>> >
>> > What's wrong and how do I fix it? I'm OK to reset my Messages back to 
>> > defaults since I just started using it and have no contacts. The only 
>> > thing was to delete defaults and send and receive a few text messages to 
>> > mobile phone numbers.
>> >
>> > Thank you in advance. :)
>
>> What messages are logged to the console and system logs when you try to
>> launch Messages?
>
> system.log:
> ...
> Aug 21 11:09:04 15inMBPretina2013 com.apple.xpc.launchd[1] 
> (com.apple.imfoundation.IMRemoteURLConnectionAgent): The 
> _DirtyJetsamMemoryLimit key is not available on this platform.
> Aug 21 11:09:04 15inMBPretina2013 Messages[64550]: schema version 8010
> Aug 21 11:09:05 15inMBPretina2013 WindowServer[157]: 
> disable_update_timeout: UI updates were forcibly disabled by application 
> "Messages" for over 1.00 seconds. Server has re-enabled them.
> Aug 21 11:09:19 15inMBPretina2013 WindowServer[157]: 
> disable_update_likely_unbalanced: UI updates still disabled by 
> application "Messages" after 15.00 seconds (server forcibly re-enabled 
> them after 1.00 seconds). Likely an unbalanced disableUpdate call.
> Aug 21 11:09:31 15inMBPretina2013 com.apple.iCloudHelper[64620]: 
> objc[64620]: Class FALogging is implemented in both 
> /System/Library/PrivateFrameworks/FamilyCircle.framework/Versions/A/FamilyCircle 
> and 
> /System/Library/PrivateFrameworks/FamilyNotification.framework/Versions/A/FamilyNotification. 
> One of the two will be used. Which one is undefined.
> Aug 21 11:09:31 15inMBPretina2013 com.apple.xpc.launchd[1] 
> (com.apple.imfoundation.IMRemoteURLConnectionAgent): The 
> _DirtyJetsamMemoryLimit key is not available on this platform.
> Aug 21 11:09:31 15inMBPretina2013 
> com.apple.appkit.xpc.openAndSavePanelService[64617]: assertion failed: 
> 14F27: libxpc.dylib + 62447 [5C829202-962E-3744-8B50-00D38CC88E84]: 0x89
> Aug 21 11:09:54 15inMBPretina2013 com.apple.xpc.launchd[1] 
> (com.apple.imfoundation.IMRemoteURLConnectionAgent): The 
> _DirtyJetsamMemoryLimit key is not available on this platform.
> ...
> Aug 21 11:10:34 15inMBPretina2013 kernel[0]: process Messages[64550] 
> thread 136893 caught burning CPU! It used more than 50% CPU (Actual 
> recent usage: 99%) over 180 seconds. thread lifetime cpu usage 90.041836 
> seconds, (89.397553 user, 0.644283 system) ledger info: balance: 
> 90007105176 credit: 90009554728 debit: 2449552 limit: 90000000000 (50%) 
> period: 180000000000 time since last refill (ns): 90229029843 
> Aug 21 11:10:34 15inMBPretina2013 com.apple.xpc.launchd[1] 
> (com.apple.ReportCrash[65525]): Endpoint has been activated through 
> legacy launch(3) APIs. Please switch to XPC or bootstrap_check_in(): 
> com.apple.ReportCrash
> Aug 21 11:10:34 15inMBPretina2013 ReportCrash[65525]: Invoking spindump 
> for pid=64550 thread=136893 percent_cpu=99 duration=91 because of 
> excessive cpu utilization
> Aug 21 11:10:34 15inMBPretina2013 spindump[1255]: Saved 
> cpu_resource.diag report for Messages version 8.0 (4760) to 
> /Library/Logs/DiagnosticReports/Messages_2015-08-21-111034_15inMBPretina2013.cpu_resource.diag
> Aug 21 11:10:52 15inMBPretina2013 jamf[65604]: CFNetwork SSLHandshake 
> failed (-9806)
> Aug 21 11:10:53 --- last message repeated 2 times ---
> Aug 21 11:10:53 15inMBPretina2013 jamf[65604]: 
> NSURLConnection/CFURLConnection HTTP load failed 
> (kCFStreamErrorDomainSSL, -9806)
> ...
>
> dmesg showed:
> ...
> process Messages[64550] thread 136893 caught burning CPU! It used more 
> than 50% CPU (Actual recent usage: 99%) over 180 seconds. thread 
> lifetime cpu usage 90.041836 seconds, (89.397553 user, 0.644283 system) 
> ledger info: balance: 90007105176 credit: 90009554728 debit: 2449552 
> limit: 90000000000 (50%) period: 180000000000 time since last refill 
> (ns): 90229029843 
> ...

So Messages is getting stuck in a state where it is using lots of CPU
resources while unresponsive. 

The messages you posted above state more information about the problem
can be found in:

/Library/Logs/DiagnosticReports/Messages_2015-08-21-111034_15inMBPretina2013.cpu_resource.diag

Can you post the contents of that file?

Question: Does Messages actually crash if you just let it sit and do
its thing for a while? If so, the crash report could be enlightening.

-- 
E-mail sent to this address may be devoured by my ravenous SPAM filter.
I often ignore posts from Google. Use a real news client instead.

JR

Back to comp.sys.mac.apps | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

Starting up Messsages app freezes and hogs CPU. ANTant@zimage.com (Ant) - 2015-08-20 14:11 -0500
  Re: Starting up Messsages app freezes and hogs CPU. Jolly Roger <jollyroger@pobox.com> - 2015-08-21 00:45 +0000
    Re: Starting up Messsages app freezes and hogs CPU. ANTant@zimage.com (Ant) - 2015-08-21 13:40 -0500
      Re: Starting up Messsages app freezes and hogs CPU. Jolly Roger <jollyroger@pobox.com> - 2015-08-21 19:25 +0000
        Re: Starting up Messsages app freezes and hogs CPU. ANTant@zimage.com (Ant) - 2015-08-21 15:21 -0500
  Re: Starting up Messsages app freezes and hogs CPU. ANTant@zimage.com (Ant) - 2015-08-21 17:19 -0500

csiph-web