Skip to main content

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

Capture One stays running after quit

James Bissette
Capture One stays running after quit in the windows task manager? Is anyone experiencing this? How can I fix it?
0

Comments

15 comments

Date Votes
  • SFA
    How long does it seem to stay running?

    Are you using catalogues?

    Do you have automatic back up set up?
    0
  • James Bissette
    It runs until I force quit it. I will have to check on the automatic backup. Just installed it the other day so I am new to C1, been using lightroom for years now. Figured I would check out C1 and see what it had to offer
    0
  • James Bissette
    I am using catalogs. Is it more beneficial to do sessions? Each event or wedding would be a new catalog or session
    0
  • Ian Wilson
    Moderator
    Top Commenter
    Sessions are ideally suited to having a new session for every event or job. There is not much advantage to using a catalog each time.

    Ian
    0
  • SFA
    [quote="NNN636966801503681750" wrote:
    It runs until I force quit it. I will have to check on the automatic backup. Just installed it the other day so I am new to C1, been using lightroom for years now. Figured I would check out C1 and see what it had to offer


    Once in a while I have have had C1 seem to run endlessly - more than a few seconds after it clears for the screen - as it tidies up after exit. (All that would do is prevent an immediate restart of another C1 instance. Wait a few secondes and all is well.)

    The cause is invariably some sort of system problem, typically running enough applications to use almost all of the RAM memory or working with extremely full discs trying to finish some jobs before taking time to tidy up. Of course lack of disc space can affect operations if memory swapping is active so both situations occurring concurrently can be really problematic.

    It is likely quite possible that any numbers for free disc capacity and memory availability may look OK but are not taking into account internal virtual memory operational requirements of the moment. So things may look better than they are if you check on performance.

    If you have killed the application in order to exit I would recommend re-booting the system - perhaps a couple of times - to allow Windows to do some internal temporary work file tidying and then the same with C1 for the same reasons.

    If you are using catalogues and auto back up then there are most likely some other consideration about the amount of time that may take to complete but as I almost never use catalogues and do not have auto backup active when I do I'm not in a position to offer any further advice other than to raise the question.

    Of course your problems may be completely different to my past experiences but are worth considering even if only to eliminate them as possible problem sources.

    HTH.

    Grant
    0
  • FirstName LastName
    My Windows7 SP1 shows same problem, while I asked Windows10 user about this problem, he didn't suffer. So I rolled back to ver.12.0.4 and waiting bug fixed version.
    0
  • James Bissette
    I am running win 7 also
    0
  • James Bissette
    Anyone successfully run Capture Pro 12 on windows 7?
    0
  • Steve Pereira
    Since updating to 12.1.0.106 I am experiencing the same issue. If I quit Capture One Pro 12 I am not able to restart it as it reports there is an instance already running. Indeed it is running, in the background as a zombie (CaptureOne.exe) and with no CPU usage and zero change in memory footprint (which can actually be quite high if I have processed a lot of images in my previous work session... so that could mean 3-4 GB of RAM just sitting there locked away from use by any other process).

    If I have processed/output an image, then upon shutdown I end up with TWO zombie processes: the aforementioned CaptureOne.exe and also an additional ImgCoreProcess.exe, both sitting there hogging memory but no CPU. It gives me the impression that some common shutdown library was updated with some faulty code.

    I'm running Windows 7. As stated earlier, the version of Capture One Pro I was running before (12.0.3.22 according to the installer application) did not exhibit this problem.

    EDIT: I just processed a shoot... after quitting, taskmanager shows:
    CaptureOne.exe 5,351,008 K
    ImgCoreProcess.exe 1,478,028 K
    That's a LOT of memory hanging after a shutdown!!!
    0
  • James Bissette
    So I went ahead and updated to Win 10. Was still able to do a free update to Win 10. Now Capture One Pro closes as it should when I quit it. Support for Win 7 stops in 2020 anyways, so we will have to update sooner or later. Just glad that fixed my issues with Capture One
    0
  • SFA
    I'm running C1 12.1 on Windows 7 (using sessions) and I do not see the problem reported above.

    That suggests it is not a fundamental generic problem.
    0
  • OlegEM
    Same problems,
    I work with sessions, CaptureOne remains in memory after closing of the program
    0
  • SFA
    [quote="OlegEM" wrote:
    Same problems,
    I work with sessions, CaptureOne remains in memory after closing of the program


    For how long?
    0
  • Permanently deleted user
    support replied that it is a known issue for win7, i bring up the task manager, select capture one and end process/close the program so as not to have to reboot the system each time.
    0
  • Steve Pereira
    Recently upgraded to version 12.1.1.19, it looks like the problem was fixed! Thanks for that, guys!

    Also, it looks like the preview generation has gotten a little more pep as things seem a bit quicker overall.
    0

Post is closed for comments.