Camouyer

Resilio at 100% CPU on Mac and hanging

Recommended Posts

Hi,

I use Resilio on an iMac and a MacBook Pro. 

The issue is on the iMac where Resilio is at 100% CPU usage and it is hanging. The GUI is extremely slow, not usable.

I have tried retsarting Resilio several time : same issue : 100% CPU and hanging.

Any hint where to look for ?

 

 

Share this post


Link to post
Share on other sites

The Resilio Sync team sent me a test version (2.5.10013 (239)) which solved this issue for me. I assume they will be rolling out the fix sometime in the near future.

Share this post


Link to post
Share on other sites

Hello,

 

Here's an update after a few days running the new version :

- At first, one of the MAC had the same behaviors, running 100% CPU, but the second worked properley

- After restarting the faulty one, everything went smoothly and the sync between the two works like a charm !

Thank you for the great support.

 

 

Share this post


Link to post
Share on other sites
11 hours ago, Helen said:

it's in 2.5.6 released recently 

FYI Neither of my Windows/macOS test clients detected a new version so I had to download the latest version manually.

Share this post


Link to post
Share on other sites

@ilyas, open peers lists and check sync queue - some files got stuck and are trying to finish syncing. have you already sent the debug logs to support? 

Share this post


Link to post
Share on other sites

Same issue here with all my Macs and Sync Version 2.5.7 (1061).

I'm working with Sync in the evening. Then I close the lid of my MacBook Pro / Air.

The next day I open the lid and the Sync App got stuck with 100% CPU usage.

Share this post


Link to post
Share on other sites

open peers lists and check sync queue - some files got stuck and are trying to finish syncing. have you already sent the debug logs to support? 

Share this post


Link to post
Share on other sites

" some files got stuck and are trying to finish syncing"

This might be the case, but in my situation, there are no peers available to sync to right now.

My NAS is offline and the other notbooks are offline too.

Maybe Sync wants to sync but cannot ... and ends up in an infinit loop.

(I'm trying to provide logs as soon as possible)

Share this post


Link to post
Share on other sites

Same issue here - Resiilo Sync 2.5.7 (1061) on macOS 10.12.6.

No files pending to sync, just idle, but after 2-3 days uptime, I feel my MacBook hot, and see 'beach ball' cursor over Sync icon in the status bar, and have to kill Sync process and restart the app again - after that everything is OK for 2-3 days.

Share this post


Link to post
Share on other sites

I have the same problem, 100%CPU, resilio apparently jammed.  Wondered why my battery was going flat so fast till I worked it out.  Resilio Sync 2.5.7 on MacOS 10.12.6 too.

 

Share this post


Link to post
Share on other sites
On 17/8/2017 at 0:25 PM, Elijah said:

Same issue here - Resiilo Sync 2.5.7 (1061) on macOS 10.12.6.

No files pending to sync, just idle, but after 2-3 days uptime, I feel my MacBook hot, and see 'beach ball' cursor over Sync icon in the status bar, and have to kill Sync process and restart the app again - after that everything is OK for 2-3 days.

I have exactly the same problem. It causes a ridiculously fast battery drain to my MacBook Air Early 2015 running macOs Sierra 10.12.6 with Resilio Sync 2.5.7.

Share this post


Link to post
Share on other sites
2 hours ago, mustgroove said:

I'm experiencing this as well, on my Macbook Pro, especially after waking from sleep

Resilio Sync 2.5.7

MacOS 10.12.6

I remember this issue did not occur in OS X El Capitan; only in macOS Sierra.

I guess I have go back to El Capitan and BitTorrent Sync 1.4.75 in order to do not have this issue again. :(

Share this post


Link to post
Share on other sites

This is what you can find in sync.log just before the issue:

[20170829 21:46:01.019] Posting message to change network to WIRED_NETWORK
[20170829 21:46:01.019] Got network change event (suggested type: WIRED_NETWORK)
[20170829 21:46:01.019] We are about network reload
[20170829 21:46:01.020] D! 14TrackerTcpConn::set_error[0x00007fe440431380][-1] 53 (network reload)
[20170829 21:46:01.020] D! 14TrackerTcpConn::set_error[0x00007fe440704230][-1] 53 (network reload)
[20170829 21:46:01.020] D! 16TunnelConnection::set_error[0x00007fe4415cb800][59] 53 (network reload)
[20170829 21:46:01.020] D! 16TunnelConnection::set_error[0x00007fe44223ce00][148] 53 (network reload)
[20170829 21:46:01.020] D! 16TunnelConnection::set_error[0x00007fe441463200][144] 53 (network reload)
[20170829 21:46:01.020] D! 16TunnelConnection::set_error[0x00007fe440884c00][126] 53 (network reload)
[20170829 21:46:01.020] D! 16TunnelConnection::set_error[0x00007fe4415bba00][114] 53 (network reload)
[20170829 21:46:01.020] D! 16TunnelConnection::set_error[0x00007fe441003800][-1] 53 (network reload)
[20170829 21:46:01.020] D! 16TunnelConnection::set_error[0x00007fe44083be00][137] 53 (network reload)
[20170829 21:46:01.020] D! 16TunnelConnection::set_error[0x00007fe4418c7a00][139] 53 (network reload)
[20170829 21:46:01.021] D! 20HttpClientConnection::set_error[0x00007fe440886800][-1] 53 (network reload)
[20170829 21:46:01.051] Joining to the multicast group 239.192.0.0:3838 on interface 192.168.179.24 (en0)
[20170829 21:46:01.051] Joining to the multicast group 239.192.0.0:3838 on interface 127.0.0.1 (lo0)
[20170829 21:46:01.052] Closing uTP tracker connection to 173.244.217.42:4000 - error 53 (network reload)
[20170829 21:46:01.052] Closing uTP tracker connection to 209.95.56.60:4000 - error 53 (network reload)
[20170829 21:46:01.472] Posting message to change network to WIRED_NETWORK
[20170829 21:46:02.192] Posting message to change network to NO_NETWORK
[20170829 21:46:02.193] Posting message to change network to NO_NETWORK
[20170829 21:46:02.397] Posting message to change network to WIRED_NETWORK
[20170829 21:46:05.162] Posting message to change network to WIRED_NETWORK
[20170829 21:46:05.171] Posting message to change network to WIRED_NETWORK
[20170829 21:46:06.161] Posting message to change network to WIRED_NETWORK

 

Share this post


Link to post
Share on other sites

@all, open peers lists and check sync queue - some files got stuck and are trying to finish syncing. have you already sent the debug logs to support? Please do. 

Share this post


Link to post
Share on other sites

Same problem here.  2 iMac's, 1 PC, and 1 MacBook Pro.  The Macs are all running macOS 10.12.6 and version 2.5.7 of Sync.  Mostly it is the MacBook Pro that hangs.  I had ego kill it and start it over again.

Share this post


Link to post
Share on other sites

Helen, thanks - system hangs, no way to open the GUI. Anywhere else to look? Where to find the debug logs? What to if I identify files that are stuck (how?)

 

Edit - just tried it again, beachball and no way to open the GUI. Appreciate more food for thought. This seems to happen after 1 or 2 days of uptime.

Edited by MrBK

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now