Search the Community
Showing results for tags 'assert failed'.
Found 1 result
Hi I keept looking into the issue I described at http://forum.bittorrent.com/topic/39034-cannot-identify-the-destination-folder-related-to-low-memory-also-possible-syncid-corruption/ a couple of days ago, and found out the "assert failed" corruption not only affected .sync/ID, but also some of the synced files!!! This a serious issue. If btsync is randomly appending these messages to some of the synced files (sometimes completely overwriting the files), it can't be trusted. This needs attention, and needs to be fixed. E.g. I found this at the end of a keepass (binary) file: [20150602 20:40:12.521] Disconnect: Is seed[20150602 20:40:12.521] assert failed /mnt/jenkins/workspace/Build-Sync-x64/fileutil.cpp:109[20150602 20:40:12.521] assert failed /mnt/jenkins/workspace/Build-Sync-x64/wincompat.h:409 Notice the date and the "Build-Sync-x64". I did modify the keepass file at that time on one of the Macs, but it seems the file got corrupted during sync to my Linux server (the assert for a Mac build is different, Build-Sync-Mac instead of Build-Sync-x64). And then the file was synced back to all systems, including the Mac where I did the edit. This happened just two days ago, running sync 2.0.120 PRO on all systems. Any sync representative can shed some light on this issue? Is it being investigated? .sync/ID corruption is annoying, but synced file corruption is a nasty bug. Regards