Re: Apparent timeouts

Tõivo Leedjärv <[email protected]> writes:

> On Fri, 26 Jan 2024 at 17:39, Dale R. Worley <[email protected]> wrote:
>>
>> Tõivo Leedjärv <[email protected]> writes:
>> > Viv's analysis of the issue is completely accurate. It is just a symptom of
>> > the GUI thread not getting sufficient run time and thus appearing "frozen",
>> > yet the actual syncing is continuing behind the scenes.
>>
>> I don't know how the Unison GUI is structured, but from these symptoms
>> it seems possible that the GUI thread doesn't run independently of the
>> file-copying thread, but instead the GUI interaction only gets to run
>> after each file is finished.  That would account for why the issue shows
>> up only when copying very large files.
>
> This is partially true. There is no full multi-threading but there is
> cooperative threading and most file operations do update the GUI
> rather frequently (users should experience the GUI as completely
> smooth).
>
> Still, there are a few operations which don't yield to other threads
> periodically. Fingerprinting a file and deleting a dir tree are such
> operations, if I'm not mistaken. Fingerprinting a large file can take
> a very long time (even minutes) and this is most likely what John is
> seeing.

I have filed

https://urldefense.com/v3/__https://github.com/bcpierce00/unison/issues/991__;!!IBzWLUs!UAmhMqS1EovR9jxxcqkp3Y_30X1uUdq6PNJEtqxhopgHllCq0k09O6hK40Omjq3whLHc8LQzsZSKZPFyEg$ 

to capture this point.   (That doesn't mean anything is about to happen;
I just like to keep state in the tracker, when it can be articulated
clearly enough for me to be sure it belongs there!)

-- 
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].