PhotoLab 9.11.0 Build 758 got stock, and couldn’t be killed by task manager or DOS or Process Explore. It even prevents soft restart. Had to hard-restart by pressing power button.
I don’t see that problem here.
May I suggest reinstalling (or repairing) PL?
Did an older version work previously?
FWIW: No problem here with PLv9.11 on Win11 either.
V9.11 is running well on my win11.
I had problems with previous versions too. The general issue is that after leaving the PL on for extended periods, say 1 week, it would behave erratically, slow response, display issue, etc, eventually leading to crash or to be killed by running task manager. The issue had been observed after I moved to Windows 11. PL9.11 is just the version I’m currently using, and in this particular case, the PL process could not be killed other than hard reset.
One observation is that the memory used by PL constantly increases, from 5GB to 16GB when it becomes problmatic, not sure if there is a memory leak (my computer has 64GB RAM).
It’s a good practice to restart any complex software as often as possible/required to prevent accumulation of minor memory leaks. DxO/Microsoft/NVIDIA, Intel, or AMD usually take care only about major memory leaks, and which are common to many users. Personally, I’ve never used PhotoLab for longer than 6 hours, or Windows for more than 16 hours before shutdown or restart (32GB RAM, RTX4070, 4k monitor, 45mpx raws here). I’ve seen major problems with VRAM leaks on NVIDIA GPUs while using AI masks in PL9/Win, but these issues are gone since PL 9.5 and 9.6. You could press DxO to investigate whether your problem is in their code, or Microsoft, or NVIDIA, or your OS config, but I think it’s more practical to shutdown PhotoLab before each lunch and shutdown Windows before going to sleep. Probably @Wolfgang does the same, so neither of us has seen your problem.
Just in case your problem is with virtual memory (not physical or VRAM), make sure you use default swap configuration in Win11 (auto). PhotoLab (or .NET underneath) is quite greedy on that, especially with 100+ mpx cameras. Forget old “good advices” for swap configuration, which work only for ancient Windows versions.
Thanks for your input. The reason for me to keep PL running is that it takes forever for it to start, on my machine. I’ve been closing/killing it periodically previously, but the recent event is severe enough for me to come here to see if it happens only to me or more broadly.
Info about my machine:
Processor 13th Gen Intel(R) Core™ i9-13900K (3.00 GHz)
Installed RAM 64.0 GB (63.7 GB usable)
Graphics card NVIDIA GeForce RTX 4070 Ti (12 GB)
Intel(R) UHD Graphics 770 (128 MB)
Storage 9.33 TB of 14.55 TB used
System type 64-bit operating system, x64-based processor
In my case it’s usually about 20-40 seconds, with about 150,000 items in the database (mostly old 12-16mpx photos), 4TB SSD internal Kingston dedicated for photos. I didn’t clean the DB yet since it was created 3 years ago by PL7 and migrated to PL8 and PL9, so it has a lot of “orphans” (references to files no more there). Last time I looked using ProcMon, it was reading the photo database which took most of the startup time. I just got used to the initial delay.
My laptop is a lower spec machine than yours (i7 13th gen, 16GB RAM, RTX 4050). On that machine from double clicking the PL icon to it being ready to use takes about 45 secs. OK that’s not exactly speedy but it’s not “forever”. How long do you have to wait to get a coffee?
In Capture One I use “sessions” instead of “catalogs”, with one “session” per year. Maybe something similar would shorten PhotoLab startup?
On the other hand, for 3 years I had no PL database corruption issues, unlike with Lightroom and their collections before. Personally, I prefer it slowly and steadily…
It’s up to DxO to decide anyway.
EDIT: Certainly a script for PL photo DB “refresh” would be welcomed. The script/program should remove all direct and indirect references to non-existent files (leaving a way for restore, of course). Managing unwanted files outside of PhotoLab control should be recognized by PL as legitimate user action. This is already a long story in the forum.