Running in background even when it is closed

[LHamel]

Hi everybody,

I recently bought PaintShop Pro Ultimate X5. So, the software is remain running in the background even when I quit the app. I must do CTRL-ALT-DEL and stop the process. Is it a bug ? I think is it not normal

[Ken Berry]

I have often found that various Corel programs, including PSP and Video Studio, seem to keep running for some time in Task Manager > Processes after I have closed the program. This usually stops me from re-opening the program a few minutes after I closed it. I then have to go to Task Manager > Processes and highlight the program entry then press the 'End Process' button.

In other words, I get the same problem as you and don't know the answer why. I have learned to live with it over the years as I appear to be only one of a very few users who have -- or at least notice -- the problem. In my case, I find that after about 10 minutes running in the background, the program does in fact turn itself off. But the really curious thing is that sometimes it also turns off immediately I close it. Go figure!

[Tadjio]

Under File / Preferences / General Program Preferences / Manage there is an option:
"Allow cataloging to complete after exiting the application"

Set this off.

[kaymann]

Tadjio beat me to the punch. However, the other side to is to know what is happening and let it go. Your system is high end enough to just let it finish up as the degregation in system resources is probably minimal.

[alanpalmer]

Yes, while PSP is building the catalog for the first time it is likely to stay in memory for some time after closure. However, once it finally completes it should quit much earlier. As kaymann indicates, let it run unless it's really affecting other work.

[LHamel]

Thank you very much. Your comments are very appreciated.

[LHamel]

Good morning,

I let go of the process (paint shop pro) overnight. This morning it is still there. I click the icon to launch the application, it will not start. I absolutely stopped the process. In addition, I have done what Tadjo wrote : Set this of "Allow cataloging to...". But, it does not work.

Have a good day.

[LHamel]

Bonjour,
Is this normal, when I work with "Paintshop pro X5", the application takes a lot of resources and the fans run at maximum speed ? Besides, he continued to work (in background) after leaving. Also, is it normal that the application is installed in the folder "Programs files (x86)" ? Thank you very much.

[kaymann]

Bonjour,
Is this normal, when I work with "Paintshop pro X5", the application takes a lot of resources and the fans run at maximum speed ? Besides, he continued to work (in background) after leaving. Also, is it normal that the application is installed in the folder "Programs files (x86)" ? Thank you very much.

I have a simular system as yours and I do not experience the resource hogging you describe.

I do not have any left over processess now that my catalog is caught up (first run only).

Most programs are true x86 (32bit) with code to dummy down the 64bit OS to allow the 32bit instruction set.
32bit v 64bit is simply the length of the instructions sent to the cpu. The longer the set, the more instructions you can create and the more memory you can put an address to. In other words the more precise your instructions can be. The more precise your instructions the quicker you get things done. PSPX5 is native 32bit so it lands in the 32bit "Program Files (x86)" folder. True 64 (as opposed to 64bit capable) programs land in the "Program Files" folder.

In your case I would kill your catalog and start again.

[LHamel]

Thank you Kaymann,

Just a question : How long does it take for your catalog is caught up ?

[alanpalmer]

That depends on how many images you have on your computer.

[LHamel]

That depends on how many images you have on your computer.

I understand very well. But, this is not normal after 24 hours. I had to stop the process to launch the application because it would not start.

[kaymann]

I have roughly 50,000 all in all and I do not ever remember going over a coulple of hours. I would usually start the catalog build and walk away. When I got back it would be done. Sorry I can not be more acccurate than that. However never 24 hours! I am begining to think your catalog is barfing on a specific photo. Wondering if there is a way you can narrow that down by last folder imported or something simular....

[LHamel]

As strange as it may seem, the problem is solved. I don't know why but is solved.

[Pantera3k]

Now is 2023. And I frequently find VS 2023 sits and eats CPU resources in the background even I closed it. Basically did it yesterday. But still found this in the morning. Memory leakage? Concurrency mining? Any thoughts?