100% CPU usage since last update (mac)

[sylar]

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!

[sylar]

Sync just crashed. I have a crash file if it can help.

EDIT : just tried with 1.1.15 version. Same problem.

[sergey@bt]

"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.

[Killa]

I have the exact same symptoms, 100% CPU and those ping in the log file.

[sylar]

"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.

[sylar]

While I had already reboot before posting this thread, it seems that this morning all is OK.

I have just started the iMac and launched BTsync, exactly like I did on Friday, and this time, no 100% CPU bug.

Very strange ...

[PowZone]

On Yosemite:

when BTSync is active, even if sync is paused, the process WindowServer boost over 100% CPU and mac becomes super slow..

 

This happens only when I run the BTSync app.

I tested it with MacBook Pro and iMac, same result.

 

I'm using BTsync 1.4.93 beta 

[RomanZ]

@PowZone

 

Couple of questions to clarify your issue:

1) Are your running Yosemite Beta or release?

2) When you see high CPU usage - is Sync main window open / minimized? If yes - can you please close it and see if issue still occurs?