100% CPU usage since last update (mac)


sylar
 Share

Recommended Posts

Hi,

I have just updated to the last available version on my iMac@work, and as soon as sync is launched, it uses 100% of my CPU. The new indexing process is finished, nothing seems to happens, but I get in the log file over and over:


[20130514 15:35:24.378] Send ping to peer (0000000000000000000000000000000000000000) for share XXX_SHAR1:
[20130514 15:35:24.378] ping 192.168.1.2:1234 directly
[20130514 15:35:24.378] Send ping to peer (0000000000000000000000000000000000000000) for share XXX_SHAR1:
[20130514 15:35:24.378] ping other_mac_ip:1234 directly
[20130514 15:35:24.378] Send ping to peer (0000000000000000000000000000000000000000) for share XXX_SHAR2:
[20130514 15:35:24.378] ping 192.168.1.2:1234 directly
[20130514 15:35:24.378] Send ping to peer (0000000000000000000000000000000000000000) for share XXX_SHAR2:
[20130514 15:35:24.378] ping other_mac_ip:1234 directly
[20130514 15:35:24.378] Send ping to peer (0000000000000000000000000000000000000000) for share XXX_SHAR3:
[20130514 15:35:24.378] ping 192.168.1.2:1234 directly
[20130514 15:35:24.378] Send ping to peer (0000000000000000000000000000000000000000) for share XXX_SHAR3:
[20130514 15:35:24.378] ping other_mac_ip:1234 directly
[20130514 15:35:24.378] Send ping to peer (0000000000000000000000000000000000000000) for share XXX_SHAR4:
[20130514 15:35:24.378] ping 192.168.1.2:1234 directly
[20130514 15:35:24.378] Send ping to peer (0000000000000000000000000000000000000000) for share XXX_SHAR4:
[20130514 15:35:24.378] ping other_mac_ip:1234 directly
[20130514 15:35:24.378] Send ping to peer (0000000000000000000000000000000000000000) for share XXX_SHAR5:
[20130514 15:35:24.378] ping 192.168.1.2:1234 directly
[20130514 15:35:24.378] Send ping to peer (0000000000000000000000000000000000000000) for share XXX_SHAR5:
[20130514 15:35:24.378] ping other_mac_ip:1234 directly
[20130514 15:35:25.382] Send ping to peer (0000000000000000000000000000000000000000) for share XXX_SHAR1:
[20130514 15:35:25.382] ping 192.168.1.2:1234 directly
[20130514 15:35:25.382] Send ping to peer (0000000000000000000000000000000000000000) for share XXX_SHAR1:
[20130514 15:35:25.382] ping other_mac_ip:1234 directly
[20130514 15:35:25.382] Send ping to peer (0000000000000000000000000000000000000000) for share XXX_SHAR2:
[20130514 15:35:25.382] ping 192.168.1.2:1234 directly
[20130514 15:35:25.382] Send ping to peer (0000000000000000000000000000000000000000) for share XXX_SHAR2:
[20130514 15:35:25.382] ping other_mac_ip:1234 directly
[20130514 15:35:25.382] Send ping to peer (0000000000000000000000000000000000000000) for share XXX_SHAR3:
[20130514 15:35:25.382] ping 192.168.1.2:1234 directly
[20130514 15:35:25.382] Send ping to peer (0000000000000000000000000000000000000000) for share XXX_SHAR3:
[20130514 15:35:25.382] ping other_mac_ip:1234 directly
[20130514 15:35:25.383] Send ping to peer (0000000000000000000000000000000000000000) for share XXX_SHAR4:
[20130514 15:35:25.383] ping 192.168.1.2:1234 directly
[20130514 15:35:25.383] Send ping to peer (0000000000000000000000000000000000000000) for share XXX_SHAR4:
[20130514 15:35:25.383] ping other_mac_ip:1234 directly
[20130514 15:35:25.383] Send ping to peer (0000000000000000000000000000000000000000) for share XXX_SHAR5:
[20130514 15:35:25.383] ping 192.168.1.2:1234 directly
[20130514 15:35:25.383] Send ping to peer (0000000000000000000000000000000000000000) for share XXX_SHAR5:

So many many "ping" at the same time. Both local machine (192.168.XXX) and other mac (other_mac_ip) are not accessible (BTsync is stopped on these machines, and the local machine is only accessible with a VPN which is not active).

On the other mac, no problem, no 100% CPU bug. And the two mac seem to sync well even with this 100% CPU bug.

Any idea? Tell me if I can do something else to help to debug!

Link to comment
Share on other sites

"Ping" packets should not cause 100% CPU. Do you see anything it log besides ping? Can you please create process sample with Activity Monitor and send it to us? Also if you saw crash with 1.1.15, send it as well.

No, nothing else in the log file. I will send you the process sample on Monday. In the meantime, you can download here the crash file created when the 1.1.12 version crashed.

Link to comment
Share on other sites

  • 1 year later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share