terafin

Members
  • Content Count

    14
  • Joined

  • Last visited

About terafin

  • Rank
    Member
  1. Thanks! I look forward to it, BitTorrent Sync is wonderful otherwise
  2. Thanks! Any luck here? It's sadly making my laptop pretty hard to use off power supply...
  3. Sure, looking at the sample: ​Date/Time: 2014-06-30 12:20:00.754 -0700 [20140630 12:19:07.269] Incoming connection from 10.0.1.201:45040[20140630 12:19:07.355] Extension: ipv4:[76.126.247.222] for '/Volumes/Rydia/Desktop/Document.txt/com.apple.FinderInfo'[20140630 12:20:08.278] Incoming connection from 10.0.1.201:45040 Nothing was logged in that timeframe "12:20:00.754" minus 30 seconds or so. Additionally, BT Sync in activity monitor and top is literally never dropping below 6-10% CPU usage. For example, the CPU time of BTSync on my machine right now (post reboot last night) is 1:43:37.95 where window server is 1:36:39.01.
  4. Attached are some samples and debug logs. I love BTSync, but it's really killing the battery on my laptop, with constant CPU usage. Let me know if you need anything at all, I'm happy to quickly attach! Thanks! sample.txt sync.txt
  5. There look to be a few things going on, however the torrent client is updating it's table view in the background: Call graph: 2484 Thread_54402: Main Thread DispatchQueue_<multiple> + 2484 ??? (in BitTorrent Sync) load address 0x1000 + 0x1fc5 [0x2fc5] + 2484 NSApplicationMain (in AppKit) + 1165 [0x97351c48] + 2484 -[NSApplication run] (in AppKit) + 727 [0x973ab95c] + 2484 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] (in AppKit) + 119 [0x973b4730] + 2484 _DPSNextEvent (in AppKit) + 1602 [0x973b5209] + 2484 _BlockUntilNextEventMatchingListInModeWithFilter (in HIToolbox) + 92 [0x94a983b7] + 2484 ReceiveNextEventCommon (in HIToolbox) + 526 [0x9493244c] + 2484 RunCurrentEventLoopInMode (in HIToolbox) + 259 [0x949326cd] + 2484 CFRunLoopRunInMode (in CoreFoundation) + 123 [0x9a74643b] + 2484 CFRunLoopRunSpecific (in CoreFoundation) + 394 [0x9a7465da] + 2421 __CFRunLoopRun (in CoreFoundation) + 1369 [0x9a747149] + ! 2421 __CFRunLoopServiceMachPort (in CoreFoundation) + 169 [0x9a740ca9] + ! 2421 mach_msg (in libsystem_kernel.dylib) + 68 [0x91c4913c] + ! 2421 mach_msg_trap (in libsystem_kernel.dylib) + 10 [0x91c49f4a] + 50 __CFRunLoopRun (in CoreFoundation) + 2515 [0x9a7475c3] + ! 49 __CFRunLoopDoTimer (in CoreFoundation) + 1354 [0x9a76202a] + ! : 49 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ (in CoreFoundation) + 22 [0x9a762666] + ! : 49 __NSFireTimer (in Foundation) + 117 [0x9284bb4b] + ! : 12 ??? (in BitTorrent Sync) load address 0x1000 + 0x8b8c4 [0x8c8c4] + ! : 11 +[NSDateFormatter localizedStringFromDate:dateStyle:timeStyle:] (in Foundation) + 147 [0x928d84e5] + ! : + 11 -[NSDateFormatter stringForObjectValue:] (in Foundation) + 301 [0x92883598] + ! : + 11 -[NSDateFormatter _regenerateFormatterIfAbsent] (in Foundation) + 39 [0x92882a6f] + ! : + 11 -[NSDateFormatter _regenerateFormatter] (in Foundation) + 364 [0x92882be0] + ! : + 11 CFDateFormatterCreate (in CoreFoundation) + 347 [0x9a7b305b] + ! : + 5 __ResetUDateFormat (in CoreFoundation) + 505 [0x9a7b32e9] + ! : + ! 5 __cficu_udat_open (in CoreFoundation) + 75 [0x9a84fcab] + ! : + ! 5 udat_open (in libicucore.A.dylib) + 355 [0x98dc1b0a] + ! 10 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ (in CoreFoundation) + 30 [0x9a76ce5e] + ! 10 CA::Transaction::observer_callback(__CFRunLoopObserver*, unsigned long, void*) (in QuartzCore) + 75 [0x93f7d64f] + ! 10 CA::Transaction::commit() (in QuartzCore) + 393 [0x93f7d849] + ! 10 CA::Context::commit_transaction(CA::Transaction*) (in QuartzCore) + 292 [0x93f7dab0] + ! 9 CA::Layer::layout_and_display_if_needed(CA::Transaction*) (in QuartzCore) + 38 [0x93f88a6c] + ! : 9 CA::Layer::display_if_needed(CA::Transaction*) (in QuartzCore) + 690 [0x93f891e4] + ! : 9 -[_NSViewBackingLayer display] (in AppKit) + 1788 [0x977e0f6c] + ! : 9 -[_NSBackingLayer display] (in AppKit) + 26 [0x97ccdbbd] + ! : 9 _NSBackingLayerDisplay (in AppKit) + 105 [0x97ccdc2b] + ! : 9 -[CALayer display] (in QuartzCore) + 20 [0x93f892ba] + ! : 9 CA::Layer::display() (in QuartzCore) + 186 [0x93f8937c] + ! : 9 -[CALayer _display] (in QuartzCore) + 20 [0x93f8939b] + ! : 9 CA::Layer::display_() (in QuartzCore) + 1552 [0x93f899b0] + ! : 9 x_blame_allocations (in QuartzCore) + 88 [0x940dd593] + ! : 9 ___ZN2CA5Layer8display_Ev_block_invoke (in QuartzCore) + 93 [0x940b354e] + ! : 9 CABackingStoreUpdate_ (in QuartzCore) + 3412 [0x93f8acca] + ! : 9 backing_callback(CGContext*, void*) (in QuartzCore) + 96 [0x940b35b6] + ! : 9 -[_NSViewBackingLayer drawInContext:] (in AppKit) + 383 [0x977e1607] + ! : 9 -[NSView(NSLayerKitGlue) drawLayer:inContext:] (in AppKit) + 115 [0x97539e27] + ! : 9 -[NSView(NSLayerKitGlue) _drawViewBackingLayer:inContext:drawingHandler:] (in AppKit) + 2085 [0x9753a70e] + ! : 9 __46-[NSView(NSLayerKitGlue) drawLayer:inContext:]_block_invoke (in AppKit) + 189 [0x97b195db] + ! : 9 -[NSView(NSInternal) _recursive:displayRectIgnoringOpacity:inGraphicsContext:CGContext:topView:shouldChangeFontReferenceColor:] (in AppKit) + 1125 [0x97a3b81d] + ! : 4 -[NSTableView drawRect:] (in AppKit) + 987 [0x97507055] I reported this to the mail email many builds ago but it still seems to be doing this. Both my Macs are doing this, is this my config, or are people seeing similar issues?
  6. Thanks, already done - awaiting a response. I'll post here if I hear anything!
  7. Is there any info we can provide here? This is a truly fantastic product, but the CPU usage is really hurting
  8. Thanks! I tried this out on all machines, and sadly it's still doing the same pings back and forth. Any other ideas? Any logs that would be useful here?
  9. Interesting. I have not, however... I can't seem to see it anywhere? Where is that at? As a note I'm also getting pings from peers off my LAN too..
  10. I tried that, sadly from logs it doesn't look like the re-scan, it appears to be pinging back and forth to clients, as well as scanning disks:[20130519 14:46:30.193] Incoming connection from 10.0.1.201:20003 [20130519 14:46:30.344] Got ping (broadcast: 1) from peer 10.0.1.201:20003 (E91B9A4E6C12E9B455F5B80B5C316501945A2161) for share 3D01228585AB14AFC849D5E36514802510695FCB [20130519 14:46:30.344] Found peer for folder /Volumes/Rydia/bin E91B9A4E6C12E9B455F5B80B5C316501945A2161 10.0.1.201:20003 direct:1 [20130519 14:46:30.344] Got ping (broadcast: 1) from peer 10.0.1.201:20003 (E91B9A4E6C12E9B455F5B80B5C316501945A2161) for share BA04BECC657B2C1D909046418535FEA63FCA9C5D [20130519 14:46:30.344] Found peer for folder /Volumes/Rydia/Desktop E91B9A4E6C12E9B455F5B80B5C316501945A2161 10.0.1.201:20003 direct:1 [20130519 14:46:30.344] Got ping (broadcast: 1) from peer 10.0.1.201:20003 (E91B9A4E6C12E9B455F5B80B5C316501945A2161) for share 01477C0E13B268157A0D2B76BF7A626A4D56DD51 [20130519 14:46:30.344] Found peer for folder /Volumes/Rydia/Documents E91B9A4E6C12E9B455F5B80B5C316501945A2161 10.0.1.201:20003 direct:1 [20130519 14:46:30.345] Got ping (broadcast: 1) from peer 10.0.1.201:20003 (E91B9A4E6C12E9B455F5B80B5C316501945A2161) for share 432FA5EF96A2187075A199B00FC256FB305A0751 [20130519 14:46:30.345] Found peer for folder /Volumes/Rydia/Movies E91B9A4E6C12E9B455F5B80B5C316501945A2161 10.0.1.201:20003 direct:1 [20130519 14:46:30.345] Got ping (broadcast: 1) from peer 10.0.1.201:20003 (E91B9A4E6C12E9B455F5B80B5C316501945A2161) for share 610ED024A291C88CC5D1F477D9084608AA01F685 [20130519 14:46:30.345] Found peer for folder /Volumes/Rydia/Pictures E91B9A4E6C12E9B455F5B80B5C316501945A2161 10.0.1.201:20003 direct:1 [20130519 14:46:30.346] Got ping (broadcast: 1) from peer 10.0.1.201:20003 (E91B9A4E6C12E9B455F5B80B5C316501945A2161) for share D155CEC3D777E90787E420A559E071420B0EB84A [20130519 14:46:30.346] Found peer for folder /Volumes/Rydia/Projects E91B9A4E6C12E9B455F5B80B5C316501945A2161 10.0.1.201:20003 direct:1 [20130519 14:46:30.346] Got ping (broadcast: 1) from peer 10.0.1.201:20003 (E91B9A4E6C12E9B455F5B80B5C316501945A2161) for share BD9F3EE6BEDBCC1F942BFA683291AF27913E432C [20130519 14:46:30.346] Found peer for folder /Volumes/Rydia/Settings E91B9A4E6C12E9B455F5B80B5C316501945A2161 10.0.1.201:20003 direct:1 [20130519 14:46:30.346] Got ping (broadcast: 1) from peer 10.0.1.201:20003 (E91B9A4E6C12E9B455F5B80B5C316501945A2161) for share 1C6BC39796D72A774733B3495E9B28D300044892 [20130519 14:46:30.346] Found peer for folder /Volumes/Rydia/Music E91B9A4E6C12E9B455F5B80B5C316501945A2161 10.0.1.201:20003 direct:1 [20130519 14:46:30.347] Got ping (broadcast: 1) from peer 10.0.1.201:20003 (E91B9A4E6C12E9B455F5B80B5C316501945A2161) for share A16D5D031C6CA1FB02E7BEB7BD6AE1BD42B84CCC [20130519 14:46:30.347] Found peer for folder /Volumes/Rydia/Applications E91B9A4E6C12E9B455F5B80B5C316501945A2161 10.0.1.201:20003 direct:1 [20130519 14:46:30.347] Got ping (broadcast: 1) from peer 10.0.1.201:20003 (E91B9A4E6C12E9B455F5B80B5C316501945A2161) for share F38B66D87F5357DAA589C3C9129FDA0652222A34 [20130519 14:46:30.347] Found peer for folder /Volumes/Rydia/Games E91B9A4E6C12E9B455F5B80B5C316501945A2161 10.0.1.201:20003 direct:1 [20130519 14:46:30.375] Got id message from peer Yuna (E91B9A4E6C12E9B455F5B80B5C316501945A2161) 1.1.15 [20130519 14:46:30.375] Got state sync request from peer E91B9A4E6C12E9B455F5B80B5C316501945A2161 [20130519 14:46:30.375] Merge: processing get_root message, my hash: 7EECEBD3A99B5939214E94B8142EF185C561669A [20130519 14:46:30.427] Merge: processing get_availability message, my hash: EBE2AE01371B0DDE40FD8668D169C3EE5FBF0EAB, prev hash: EBE2AE01371B0DDE40FD8668D169C3EE5FBF0EAB [20130519 14:46:30.454] State sync finished for folder /Volumes/Rydia/Desktop [20130519 14:46:31.040] Sending broadcast ping for share 3D01228585AB14AFC849D5E36514802510695FCB
  11. Odd, the file didn't attach, trying again! macbook.txt
  12. My Laptop and NAS SSDs are constantly being woken, and both the CPUs are constantly running at 10% or so CPU. Attached is a debug log from my mac, happy to do so from my NAS too, but can't figure out how to do it. Any ideas about how to quiet them down? I love the sync client, but it's killing my battery life - and likely impacting the SSDs