Sync Lockup after v3.8

[jfox562]

The last version that has worked for me is v3.8. Any version after this locks
up my computer until I disconnect my network cable. I believe the cause is I
am syncing 5 gig of files to a network drive. Once I get my computer unlocked,
the only file I have in the destination network location is a 4.0 gig file
named "sync.ffs_lock". I think the network drive limits a single file size to
4 gig for some reason. I don't know this for sure, but it's curious that the
file size is exactly 4.00 gig. Even if I select 7 meg of files to sync, the
program creates a 4.00 gig file on the network and then locks up. Is there a
work around for this problem?

[Zenju]

> 4.0 gig file named "sync.ffs_lock
Ths file is supposed to be not larger than a few bytes. I had a look at the
source and there is one critical section that may explain this behavior:
Usually, each five seconds, the file pointer is set to the end of the file and
a single byte is appended. Setting file pointer returns a status code. If it
fails it returns INVALID_SET_FILE_POINTER, which is 4 Bio, which is the size
of 4 Gig. But I checked for this condition, so this shouldn't be possible. If
nothing else gives a clue, I'll prepare a logging version of FFS to track down
this issue. But first a few questions:

Are you using 32 or 64 bit version?
Is the issue reproducible?
How large exactly (in bytes) is the sync.ffs_lock file?

[jfox562]

Thanks for your reply. I'm running WinXP 32 bit at work. Yes it is
consistently repeatable. It happens immediately after the hitting start after
the small window indicating what files will be deleted, copied, from left or
right. Not a single file is transfered. I'm not at work so I can't give you
the exact file size but I can tell you the properties of the file indicated
4.00 Gig. I'll update this thread on Monday with the exact file size.

[Zenju]

> Yes it is consistently repeatable
Very nice! Then I'm positive to track this issue down.

First I'll need the detailed filesize. Please check this before doing further
tests, as the file will be deleted by subsequent FFS runs.

Additionally I've created a modified version, that reports via a messagebox if
it detects something wrong:
[404, Invalid URL: http://www.file-upload.net/download-3153494/FreeFileSync_Win32.7z.html]
Please send me the info (if you get one). If you don't get any messagebox but
still are able to reproduce the issue, then I'll create a logging version to
see what's going on.

[jfox562]

If you don't mind, please create the log version because I have never received
an error message. The program simply locks the computer. When I attempt to
Ctrl-Alt-Delete, I get what appears to be normal where a prompt allows me to
go into task manager to kill a program but in my case I get a cleared desktop
but no box until I remove the network cable. I short while later the normal
box appears. I can try the version found at your provided link but I don't
believe anything will be sent. Whoops, I miss read the description. So this
version is supposed to give me a message before the lockup and this message
will assist you in troubleshooting the problem. I will download and try
tomorrow. Thanks

[Zenju]

Thanks! If the issue is due to creating this large 4 Gig file, then I expect a
messagebox with detailed info. And please don't forget to note the filesize
(in bytes) of the old sync.ffs_lock file, this may also help troubleshooting.

[jfox562]

Using original exe file from the 3.13 install the sync.ffs_lock file size is
4,194,304 kb. In the properties window for this file the sizes are "size:
3.99GB 4,294,967,295 bytes size on disk: 4.00GB 4,294,967,296 bytes". Using
the new exe from the link you provided, no message appeared before the lock
up. I conducted the same sync process as before and I did notice that the
program this time did not create a no sync.ffs_lock file on the network. I did
get an error message using both exe's when I unplugged the network cable to
unlock the computer and the program free'd up enough to show the message
"Error creating directory: {drive path}" then on another line "Windows Error
Code 64: The specific network name is no longer available." This is probably
due to the fact that I have the network cable end in my hand. Hope all of this
info is helpful. Thanks.

[Zenju]

>4,294,967,295
This is -1 represented as a 32 bit integer, exactly the error code that is
checked when setting the file pointer. Therefore this cannot be the cause,
unless there is a bug in this Windows function.
It seems this is just the sympton of some other issue.

To check whether it is related to locking file, here's a version without it:
[404, Invalid URL: http://www.file-upload.net/download-3156279/FreeFileSync_Win32.7z.html]
Can you still reproduce the issue? If so, can you confirm, that v3.8 was
working, but v3.9 does not? In this case I'll have a deeper look at the
differences between these versions (one of which was the lock file)

[jfox562]

Unfortunately, I am unable to download this file at work from that location. I
will download it at home tonight and try it tomorrow. I'm assuming the new
file is still v3.13. Regarding 3.8 to 3.9, I can confirm that a similar
problem occurs when I tried 3.9. However, I can't confirm the details; such as
file size..., but the symptoms were the same. I am using 3.8 and it works
great.

[jfox562]

Good news. The last file worked without locking up.
Here's the content of the log file that was created:
icon_buffer.cpp, LINE 316 | start work
icon_buffer.cpp, LINE 322 | 1
icon_buffer.cpp, LINE 341 | thread interrupt

[Zenju]

Now here's the real test: New version with modified locking:
[404, Invalid URL: http://www.file-upload.net/download-3167101/FreeFileSync_Win32.rar.html]

[jfox562]

Thanks. I'll download tonight and test tomorrow.

[jfox562]

Well, I'm now at work and just realized that I did download the file last
night. Would it be possible to email the file to me? Thanks

[Zenju]

Sure, send me an email and I'll reply.

[jfox562]

Aaaaa, I'm having a 'brain fart' where do I find your email address? I don't
see it under your profile.

[jfox562]

Oh, never mind, I found how to do it. It doesn't specifically say email.
You've got mail...

[bjf2000]

Would either of those help with the situation where things stop working when
it's "waiting while directory is locked," re sync.ffs_lock? It then counts
down from 23 to 16 secs or so before stopping and looping back. Deleting the
(small) lock file doesn't change anything.

[Zenju]

The issue discussed here is about a certain lockup when writing the lock file.
Message "waiting while ..." however means that the other file is still used by
another FFS instance. This is seen by " stopping and looping back": If FFS
detects changes to sync.ffs_lock while waiting, this is seen as a "life sign".

If you still feel there is some issue that needs to be addressed please open a
new thread or tracker item.

-Zenju