Memory issues after upgrade to 2024-09-23 Windows

[MSchenk]

so once more I will revert to the last working version 2023-05-15.

[PeterP]

Sorry, should have asked if you're running 32-bit or 64-bit version first, above was for 32-bit which doesn't work properly on 64-bit Asset install
64-bit version of the exe-

https://www.dbpoweramp.com/beta/Asset-2024-10-22-hotfix/uMediaLibrary.exe

[MSchenk]

I can confirm that with the 64Bit uMediaLibrary.exe scanning is working and I do not see anymore those hundreds of uMediaLibrary processes in RamMap but...

- memory issue is still the same I don't see any improvement here.
- scan speed comparing to 2023-05-15 is much slower.

[PeterP]

Can you please enable debug logging ( Advanced Settings / General Settings / [x] Output Debug Log ), fully restart Asset for good measure (cycle Asset Running Mode to "disabled" and back), let it run until memory usage goes beyond, say, 100MB, then send written debug logs to me ( peter@dbpoweramp.com ) ?
Thanks.

[IndyBaird]

I would like to add that I am seeing the same memory growth with my setup:

Windows 11 Pro 24H2
AssetUPnP Version: 2024-12-16 (64-bit)

Has anything been determined from the investigation in this thread?


Bill

[PeterP]

Verified workaround is to disable folder monitoring functionality
1) Disable "detect & catalog new tracks" - which then requires manually clicking 'rescan' to pick up new changes
or
2) Set "forced rescan interval", which causes automatic periodic checks for changes.

[IndyBaird]

Last night I did indeed discover that I could eliminate the memory growth by disabling the "detect & catalog new tracks" feature. It's good to hear that that's an "approved" workaround - thank you.

I do hope that a fix is in progress for this - I very much like the "detect & catalog new tracks" feature!


Bill

[PeterP]

Attempted fix:
Link
Copy both executables to Asset directory, re-enable indexing.
Changes have been made to prevent memory usage from accumulating (relevant process gets restarted in a manner that should not interrupt usage).

[IndyBaird]

I'll give the attempted fix a go. Thanks!


Bill

[IndyBaird]

No, I don't believe the fix worked.
I loaded the new binaries, and re-enabled indexing.
I was gone from the house for seven and a half hours, so I wasn't playing music or dropping new files on my music server.
When I had first started the system with the new binaries, it was at 30% Used Physical Memory. When I got back home, Resource Monitor showed 86% Used Physical Memory.
If anything, the fix might be keeping memory faster than the original problem.


Bill

[PeterP]

Okay, new attempt coming up, I believe I have identified the actual cause this time.
Please try these two, #1 first, #2 if the former doesn't help (restores old version behavior).
try #1
try #2

[IndyBaird]

I'll give it a go. Thanks!


Bill

[IndyBaird]

I loaded the original Asset-uPNP.exe and the uMediaLibrary.exe from try1.zip, and re-enabled indexing.
I let it operate for 12 hours, playing some music.
When I first started the system with the try1 binary, it was at 32% Used Physical Memory. At the end of twelve hours, Resource Monitor showed 33% Used Physical Memory.
This seems quite encouraging.

Thank you!

Bill