Camouyer Posted July 10, 2017 Report Share Posted July 10, 2017 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 ? Quote Link to comment Share on other sites More sharing options...
Headsoft Posted July 10, 2017 Report Share Posted July 10, 2017 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. Quote Link to comment Share on other sites More sharing options...
Helen Posted July 11, 2017 Report Share Posted July 11, 2017 Even more fixed are in 2.5.10015 build Quote Link to comment Share on other sites More sharing options...
Headsoft Posted July 16, 2017 Report Share Posted July 16, 2017 On 7/11/2017 at 4:07 AM, Helen said: Even more fixed are in 2.5.10015 build When will it be released? Quote Link to comment Share on other sites More sharing options...
Helen Posted July 17, 2017 Report Share Posted July 17, 2017 it's in 2.5.6 released recently Quote Link to comment Share on other sites More sharing options...
Camouyer Posted July 17, 2017 Author Report Share Posted July 17, 2017 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. Quote Link to comment Share on other sites More sharing options...
Helen Posted July 17, 2017 Report Share Posted July 17, 2017 *thumbs_up* Thanks! Quote Link to comment Share on other sites More sharing options...
Headsoft Posted July 17, 2017 Report Share Posted July 17, 2017 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. Quote Link to comment Share on other sites More sharing options...
Helen Posted July 18, 2017 Report Share Posted July 18, 2017 may be because it had not yet been pushed to autoupdate yet. Quote Link to comment Share on other sites More sharing options...
ilyas Posted July 24, 2017 Report Share Posted July 24, 2017 2.5.6, cpu still high. Everything is indexed and nothing trasfering. Quote Link to comment Share on other sites More sharing options...
Helen Posted July 26, 2017 Report Share Posted July 26, 2017 @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? Quote Link to comment Share on other sites More sharing options...
InSync Posted August 16, 2017 Report Share Posted August 16, 2017 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. Quote Link to comment Share on other sites More sharing options...
02384098203948234 Posted August 16, 2017 Report Share Posted August 16, 2017 I am running Resilio Sync on my MacBook Pro (Retina, 13", Ende 2013, macOS Sierra (10.12.6)). Since I have upgraded from 2.5.6 to 2.5.7 I have been experiencing around 90-100 percent CPU usage by Resilio Sync. Quote Link to comment Share on other sites More sharing options...
Helen Posted August 17, 2017 Report Share Posted August 17, 2017 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? Quote Link to comment Share on other sites More sharing options...
InSync Posted August 17, 2017 Report Share Posted August 17, 2017 " 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) Quote Link to comment Share on other sites More sharing options...
Elijah Posted August 17, 2017 Report Share Posted August 17, 2017 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. Quote Link to comment Share on other sites More sharing options...
RichardN Posted August 24, 2017 Report Share Posted August 24, 2017 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. Quote Link to comment Share on other sites More sharing options...
Andres V G Posted August 27, 2017 Report Share Posted August 27, 2017 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. Quote Link to comment Share on other sites More sharing options...
mustgroove Posted August 28, 2017 Report Share Posted August 28, 2017 I'm experiencing this as well, on my Macbook Pro, especially after waking from sleep Resilio Sync 2.5.7 MacOS 10.12.6 Quote Link to comment Share on other sites More sharing options...
Andres V G Posted August 28, 2017 Report Share Posted August 28, 2017 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. Quote Link to comment Share on other sites More sharing options...
MrBK Posted August 29, 2017 Report Share Posted August 29, 2017 Same here. 2 Macs, 1 iMac and 1 Macbook. Both Mac OS 10.12.6, Resilio Sync 2.5.7. Quote Link to comment Share on other sites More sharing options...
InSync Posted August 29, 2017 Report Share Posted August 29, 2017 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 Quote Link to comment Share on other sites More sharing options...
Helen Posted August 30, 2017 Report Share Posted August 30, 2017 @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. Quote Link to comment Share on other sites More sharing options...
Michael Capps Posted August 30, 2017 Report Share Posted August 30, 2017 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. Quote Link to comment Share on other sites More sharing options...
MrBK Posted August 30, 2017 Report Share Posted August 30, 2017 (edited) 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 August 30, 2017 by MrBK Quote Link to comment Share on other sites More sharing options...
Recommended Posts
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.