[Mac Client Gets Stuck/crashes When Receiving Non-Ascii File Names From Linux Peer]

Today I encountered a problem where the Mac client (1.3.109) gets stuck or crashes when attempting to sync files that contain certain non-ASCII characters from a Linux (ARM) host. From the debug log, it seems that the client, after downloading the last block, tries to commit the file to the Mac's file system, and then the file system rejects the file name, leaving the process stuck.

 

After renaming the file on the Linux host and restarting the Mac client, the client happily syncs the file (and in my case, gets stuck on the next file...).

 

I see the following relevant messages in the debug log:

 

[20140816 20:09:30.984] /Users/xxx/cd2/31 - L?tzenkirchen - Counterfunk (Original Mix).mp3: Piece 80 complete

[20140816 20:09:31.036] /Users/xxx/cd2/31 - L?tzenkirchen - Counterfunk (Original Mix).mp3: Piece 92 complete

[20140816 20:09:31.070] /Users/xxx/cd2/31 - L?tzenkirchen - Counterfunk (Original Mix).mp3: Piece 130 complete

[20140816 20:09:31.084] /Users/xxx/cd2/31 - L?tzenkirchen - Counterfunk (Original Mix).mp3: Piece 191 complete

[20140816 20:09:31.124] /Users/xxx/cd2/31 - L?tzenkirchen - Counterfunk (Original Mix).mp3: Piece 114 complete

[20140816 20:09:31.164] /Users/xxx/cd2/31 - L?tzenkirchen - Counterfunk (Original Mix).mp3: Piece 193 complete

[20140816 20:09:31.193] /Users/xxx/cd2/31 - L?tzenkirchen - Counterfunk (Original Mix).mp3: Piece 163 complete

[Process gets stuck, no more logging from here on]

 

 

 

The Mac console shows the following right after this happens:

 

16-08-14 20:09:31,238 BitTorrent Sync[813]: *** setObjectForKey: object cannot be nil (key: FILE)

16-08-14 20:09:31,239 BitTorrent Sync[813]: (

0   CoreFoundation                      0x99610471 __raiseError + 193

1   libobjc.A.dylib                     0x9a27c091 objc_exception_throw + 162

2   CoreFoundation                      0x994f76c2 -[__NSDictionaryM setObject:forKey:] + 1042

3   BitTorrent Sync                     0x0008b5fd BitTorrent Sync + 566781

4   Foundation                          0x9848976b __NSFireTimer + 117

5   CoreFoundation                      0x99569ea6 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 22

6   CoreFoundation                      0x99569863 __CFRunLoopDoTimer + 1395

7   CoreFoundation                      0x995e406d __CFRunLoopDoTimers + 349

8   CoreFoundation                      0x99521353 __CFRunLoopRun + 1779

9   CoreFoundation                      0x995209ea CFRunLoopRunSpecific + 394

10  CoreFoundation                      0x9952084b CFRunLoopRunInMode + 123

11  HIToolbox                           0x998c5b5d RunCurrentEventLoopInMode + 259

12  HIToolbox                           0x998c58e2 ReceiveNextEventCommon + 526

13  HIToolbox                           0x998c56bd _BlockUntilNextEventMatchingListInModeWithFilter + 92

14  AppKit                              0x90c88349 _DPSNextEvent + 1602

15  AppKit                              0x90c87870 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 119

16  AppKit                              0x90c7a15c -[NSApplication run] + 727

17  AppKit                              0x90c62ff8 NSApplicationMain + 1165

18  BitTorrent Sync                     0x0008e929 BitTorrent Sync + 579881

19  BitTorrent Sync                     0x00002b45 BitTorrent Sync + 6981

)

 

 

Please fix the Mac client so that it does not try to save files with characters not allowed by OS X. For me it would be okay if Sync removes the characters from the file name (or encodes them using urlencoding, for instance). 

By the way, I've been syncing folders with these files for over a year now between two ARM boxes, without issue...

A related issue is that the file system on the ARM Linux boxes is case-sensitive, whereas my Mac's file system is not. So if the ARM box has two files "A.txt" and "a.txt", syncing gets stuck on the Mac end as well..