AirDC++ Forum

Hello everyone,
I think that real-time monitoring is not working in v3.54 for W7. I noticed that there is also increased RAM consumption (at v3.53 compared to v3.52), under the same conditions as shared files and OS (1591547 shared files - 12.89TB, W7 x64)
I went back to 3.52 for this reason.
Are there others with the same problem?

P.S. I also tried on W10 x64, here is working well the real-time monitoring! Fewer shared files, but I do not think that's the problem

I can confirm that share monitoring is not working on Windows 7 starting from version 3.53.

What kind if increase are you seeing in memory usage?

Yes, I noticed that at 3.53 it also did not work for the W7 and I was hoping that at 3.54 it would be okay.
My observations are on 3.53. Since real-time monitoring was not working, I had set refreshing of shared files to 60 minutes. At startup, everything is fine, but after a few days, the consumption of RAM rises several times (between 400-700MB is in normal operation and once it reached to 3-4GB and even more). With the same amount of shared files and without any transfer when hash starts the consumption of RAM increased, then it does not drop enough as before and each time it remains increased by a dozen or more MB. I do not know if I could explain well. That's what I notice at first glance, but there may be another reason.

maksis wrote:I can confirm that share monitoring is not working on Windows 7 starting from version 3.53.

Will there be a fully working version for W7 of AirDC++ with support for TLS1.3 in the future?

So the memory usage increases because of share refreshes? If it doesn't cause your system to run out of memory, then it's totally normal. That's just how Windows manages memory and I think it has been discussed on this forum before.

bobo wrote:Will there be a fully working version for W7 of AirDC++ with support for TLS1.3 in the future?

There will be a solution for using share monitoring on Windows 7. The issue is most likely caused by updates for Microsoft's developer tools that are being used for compiling the application. They will publish a major update in about a week so I'll check then if the issue still persists.

On my Windows7 computers I went back to 3.52, which works perfectly (using less than 1GB of RAM for about 13TB shared files - 24/7). I'll wait for some solution in the future. Thanks for your response!

Related to viewtopic.php?f=7&t=4801

This should fixed in the latest beta release

How to get beta versions: viewtopic.php?f=8&t=16&start=25#p9344

Sorry for the delay! I confirm! In v3.55b works normally as before. Тhanks a lot. If I notice anything else, I will write right away.
Once again, thanks for your quick reaction!