illustrate
Products            Buy            Support Forum            Registrations            Professional            About           
 

Memory issues after upgrade to 2024-09-23 Windows

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • MSchenk

    • Jul 2014
    • 24

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

    Comment

    • PeterP
      Super Moderator
      • Jul 2011
      • 1480

      #17
      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-

      Comment

      • MSchenk

        • Jul 2014
        • 24

        #18
        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.

        Comment

        • PeterP
          Super Moderator
          • Jul 2011
          • 1480

          #19
          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.

          Comment

          • IndyBaird

            • Jan 2018
            • 11

            #20
            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

            Comment

            • PeterP
              Super Moderator
              • Jul 2011
              • 1480

              #21
              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.

              Comment

              • IndyBaird

                • Jan 2018
                • 11

                #22
                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

                Comment

                Working...