• Content Count

  • Joined

  • Last visited

About shawnv

  • Rank
    New User
  1. Yeah, after I updated the peers to a newer client version, it still has a very high CPU usage. as in greater than 50% almost always. I also am unaware of what version this behavior started occurring.
  2. I also have some older peers... running 1.3.94 I'll try upgrading them and see if that helps.
  3. I don't think it's too much for it, because it worked just fine in the older versions. It's probably just a bug of some sort. If they don't get this fixed soon, I'm probably just going to download an older version and install it.
  4. I'm having the same issue. It's using a lot more CPU on idle, and I'm running it on ubuntu intel 64 bit.
  5. I think this is related to my post here and it only happens on ubuntu with the new version 1.3.80 this wasn't happening before on 1.2.X
  6. Upon further inspection, it seems like it is fine when there is a 4.1GB directory by it's self. Once I add a 200GB file it stops syncing, uses a high cpu amount, and starts reporting "Don't have permissions to write to the selected folder." on both directories after a couple of minutes of scanning, and appears to have stopped scanning the large 200GB folder after 6.6GB. Also, after reading the logs, it seems that the issue is "ReadFromDisk: Too many open files"
  7. I'm having this same issue. problem started with version 1.3.80 using btsync-user on ubuntu linux. how would I make a core dump?