Andrey D

I've noticed this behavior as well, on a 64-bit Windows machine with 8GB RAM, with fairly large share (~3TB). Adding few big files to it, will cause ST's RAM usage...

So I reproduced this again (on Win 64 system) and grabbed a bunch of pprof reports over the course of the test: before the addition of the files, during the...

Thanks for taking a look :) The largest profile is actually 1719MB (you can see it here: https://send.firefox.com/download/e45dac775f3b25a4/#iFAOQRmCaBWAaCreV7pCog). As for connections - the ST instance profiled is actually pretty light...

Copying profile is messy and not a real solution So, yes, maybe leave it open for now, and just keep it in mind during future refactors

Thanks for considering the requests. --- Off topic: Your SW seem to be very promising: it's fast, responsive and have the basics: folders, back-fwd navigation, some basic customization. Coming from...

What is your intent of "question" label? A question to the OP? Or "the legitimacy of the issue is in question for now"?

That's good, however the issue is about providing a visual clue to the user that there is a reason to scroll in the first place (more items in the folder...

As in "live display" for the seconds left until the next scan? While I can see that is can be "kinda nice" to see the internal clocks of it and...

So there is no way of differentiating "initial index exchange" from "just some index update for a new file that was just added"?

> There could be a protocol message that says “index complete, that’s all I have to send”, and we could then show “unknown” instead of out of sync until we...