CO21 leaves process running after closing the software (bug?)
While testing out the new CO21 I noticed that when I close the application after I have opened a session, the software only closes the visible window, but not the actual process. My task manager of Windows shows that there is still the actual Capture One Process (and sometimes another imaging process related to it) running in the background, taking up quite a lot of memory. This process does not shut down when you close or exit CO21. This process will only shut down when I do it manually inside the task manager.
Interestingly this problem seems to exist only when I am working or opening a session (or catalogue) with pictures in it. When I open a new session with no pictures in it, and close the software then, it shuts down as it should with no process left in the background.
This is not a good thing.
Can anyone please check if they experience the same thing on their Windows 10 (or also maybe Windows 7) machines?
With CO12 or CO20 I did not have or experienced this problem.
-
Johannes,
The C1 processes can run for a short while after the main screen has disappeared. Usually for not more than some seconds whilst some admin processes to do with writing from memory are completed. It is unusual but possible.
There is also the question of the catalog backup settings if you are using catalogs.
Sometimes the process seems to hang. Randomly. I have never worked out why.but it seems to go into such a slow state that it never ends. The Log files seems to suggest attempting to write to files. Since it is a rare occurrence for me (in all versions over the years but mainly when I am using most of the memory (multiple applications open and active) and have disk usage very close to the limits of running capacity. Sometimes if I am writing to an external drive or NAS which may have slipped into hibernating energy saving mode and be reluctant to wake up.
On the rare occasions the phenomenon seems to repeat all the time rather than just happen once, I will re-boot the PC (Win 7 in my case) 2 or 3 times to give Windows plenty of opportunity to tidy up orphaned work files and similar before restarting Capture One.
If the problem still persists then I tend to head towards generating some additional disk space on my system drive before doing anything else.
One or more of those activities usually see the problem go away.
I cannot guarantee that of course but it is worth a try since killing the process will likely leave so work files to be tidied up anyway.
0 -
Yes, I am able to confirm 5 minutes after closing C1 v21 I still have CODiagnosticsService.exe (child of CaptureOne.exe) still running with about 1MB RAM and 12 threads utilizing less than 1% of CPU time.
This is on W7
This may not necessarily be a bug, but the way they capture errors in C1.
0 -
Rob,
Bear in mind that from V21 Windows 7 is not officially supported.
I stopped beta testing (beta 5) when I heard that since there seemed to be problems on my system getting things to start reliably.
Shutting down might also be a problem. I had seen things earlier but not consistently.
I don't know what Diagnostic services does.
0 -
Johannes,
I can confirm. After closing C21 on Win10, it keeps running with ~17% CPU usage and 2.2 Gb RAM. It is running now for more than 5h like that. Apart from a quite substantial cpu consumption for nothing, I cannot restart C21 as only instance is allowed to run. So I need to manually kill the task (which then results in a message when I restart if I would like to send the crash report) before I can restart C21.
I repeatedly had to restart as C21 has created new previews but when I look at the image in the viewer it is all blury and cannot edit them. Also the thumbnails stay black once I select the first picture. I am very frustrated as I was planning to edit some pictures this weekend. Checking now if I can reinstall C20 until the software is further debugged. Quite disappointing.
0 -
Thank you so much for your answers, everyone.
@GK: Thank you for testing it on Windows 10. I almost figured that it will happen there too. It's similar in my case. The process left takes up over 1GB RAM.
I made some screen shots to illustrate the issue a bit more. Please see pdf here:
https://www.dropbox.com/s/t4lkcxyekbcaaqp/Capture%20One%2021_Shut-down_Problem.pdf?dl=0So far, I tested it on my Win7 PC (16GB ram). But also planning to use CO21 on another Win10 PC, if it would work fine. The upgrade only makes sense to me if it works on both machines. If not I would stick to CO20.
So I hope the team from Capture One will fix this issue in the near future.
By the way, what is the proper or best way to report bugs to the CaptureOne team?
-----------------------------
I know Microsoft and CaptureOne are not support by Microsoft and Makers of CaptureOne anymore. But since CO21 is supposed to work with Win8, I figure running it on Win7 should also still be fine. I just like Win7 a lot better than Win10.0 -
Johannes,
The official way to report bugs and obtain personalised support is to use the "Submit a request" option to create a Support Case. It can be found on most Community support pages although not highly obvious if you don't know about it.
However bear in mind that if reported only for Win 7 it will be regarded as unsupported and if reported for Win 10 and fixed for Win 10 (or even 8 and above thought there are probably very few people running 8 these days. I do not recall anyone ever admitting to doing so in the forum discussions!) there is no certainty that it would also be fixed for Win 7 since the system software components may be different enough, system to system, to prevent the provision of a universal fix.
Like you I like to stick with Win 7. I hear to many reports of Win 10 suffering from updates that are less than perfect. One of the benefits of Win 7 is that no one at Microsoft is messing around with it any more. At least not form the inside. I am sure they will soon force people to move by messing things up from the outside.
0 -
SFA,
Thank you for your further reply. I was hoping that there is a special bug reporting site. Because I did send the issue in already by "Submit a request". But since I use Win7 the feedback I got was basically, that they do not support Win7 anymore. I asked the guy if he could test it on his Win10 machine. But it seemed like the people on the support line are not able to do it. I guess they are only there to answer questions, but not going into some tests.
Since GK reported the similar issue on Win10, I might go ahead and send them another request reg. Win10 this time.
Yes, with Win7 I think the same as you. I am not a fan of all those “secret” updates and permanent changes with Win10.
0 -
I'm running v21 on Win10 using session only and everything shuts down as expected.
Nothing left running in Task Manager.
Working with the beta, v20 and v12 together, C1 has always been fanatical about not
letting more than one CaptureOne.exe process run at a time so something pretty wrong if two are showing up together.0 -
gb,
yes, in my case it can even be more than just two processes. Depending on how often I start and close CO21. Each time it leaves one process open and behind.
Though it seems like this left-over process is mainly a big amount of data left over in memory, not causing much load on the CPU. At least in my case.Another thought I had at first, maybe I do have this problem, because I had 3 different versions of CO installed on my system for testing. Not running at the same time, but installed: CO12, CO20 and CO21. Now I deinstalled all of them like described on the CO webpage: Capture One > FAQ > Installation: “How to uninstall Capture One?”
Now, I have only CO21 installed, but unfortunately the issue is still there. Same thing, closing the software leave a process using up memory behind.Strangely with any of the other previously installed Versions (CO12 or CO20) I never did have this problem. Everything worked fine and there were no processes left after closing the app.
-------------------------
I just send the CO Team a but report about this issue via "submit a request". Hopefully this time it will reach the proper person.
0 -
Johannes,
I managed to solve it: maybe it helps in your case as well: I had the impression that some background task must not be finished and that this keeps C1 running on my machine. I was unable to edit images or also export them. But interestingly enough after restarting C1 (i.e. killing the task first as only one task is allowed to run but never stops), the image appread with my adjustments. So I figured it might be related to a graphic driver issue or so that keeps it from updating an image in the viewer. In the forum I also read about corrupt monitor files (which was not the case here but I figured there might be related issues).
While it was never an issue until last week, I now updated all drivers and switched the resolution on my 4k monitor to scale with 100% instead of 125% and also to use HDR. Also, Win Update informed that there was an update that it could not complete because of another activity preventing it (whatever that means). So I did that as well.
It now works just fine and I can even load the catalogs again that did not work earlier. I now have to check if the scale and/or HDR would have in impact. But now I can close C1 and it has no tasks running.
Maybe what I did can help in your case as well. Good luck
0 -
Thanks for the update GK.
What video card do you have?
If Nvidia did you use the Studio drivers?0 -
Johannes you might have a look at the C1 log files for any clues:
C:\Users\username\AppData\Local\CaptureOne\Logs
0 -
Johannes, I just have an onbaord "integrated graphics processor- Intel® UHD Graphics support" on my asus MB. Either the Intel driver update for this one or the Chipset or the Win Update that was stuck had a correlation with the issue. It was something with .net (KB4586876). Maybe anything of that helps.
0 -
GK and gb: Thanks very much for your further info and suggestions.
I did update my Bios and graphic chip drivers now, along with many other testing, but unfortunately it did not solve the issue.
I have two graphic chips in my Dell Notebook (Intel HD Graphics 520, AMD Radeon R7 M360). I also changed the energy settings for the AMD graphic card/Chip in the AMD Catalyst Control Center, but that resulted only in artefacts on my screen while trying to use CO.I also tried different hardware acceleration settings inside CO (Preferences > General). But no change.
@GK since you mentioned .NET Framework, just did check that as well. First, I had high hopes about this one, because I noticed on my system there was only .NET Framework v.4.5 and v4.8 installed. But not v4.7, which is mentioned by CO on the website when you download CO21:
“* Support for Capture One 21 on Windows 10 is supported for builds supporting .NET 4.7 - This is currently from build 1607 through to build 20H2.”Even though it is related to Win10, I gave it a try on my Win7 system and installed .NET 4.7.2. But again, no change, same problem still. Or maybe I need to install the .NET first and then after this the CO21?
I will look into the log files. But that will be kind of new territory for me. Which one of the log files should I look into the most?
0 -
"Which one of the log files should I look into the most?"
I'm no expert but the Application.log seems to be the easiest to read/start with.
Just thought there might be some clue at the end of any of those logs that mentions something not being able to be shut down.
eg. part of normal application log ending:
[2020-12-15 22:06:15.932][000][ID:001, Main]{FS } | Waiting for thread to stop: '[FileSystem] Scheduler ItemUpdate' Timeout [MS]: 4999
[2020-12-15 22:06:15.932][000][ID:001, Main]{FS } | Thread stopped : '[FileSystem] Scheduler ItemUpdate'
[2020-12-15 22:06:15.933][001][ID:065, [File Syst]{FS } | INFO : Terminating thread : [File System] Locking Manager Dispatcher
[2020-12-15 22:06:16.120][187][ID:001, Main]{APPL } | Closing app: Closing OpenCore
[2020-12-15 22:06:16.120][000][ID:001, Main]{APPL } | Closing app: Closed OpenCore
[2020-12-15 22:06:16.120][000][ID:001, Main]{APPL } | Stopping IC
[2020-12-15 22:06:16.316][195][ID:001, Main]{APPL } | Cleaning up temporary files
[2020-12-15 22:06:16.317][000][ID:001, Main]{APPL } | Cleaning up temporary files in C:\Users\gb\AppData\Local\Temp\CaptureOneTemp1 ...
[2020-12-15 22:06:16.317][000][ID:001, Main]{APPL } | Temporary file clean up completed
[2020-12-15 22:06:16.317][000][ID:001, Main]{APPL } | Shutdown of managers and cores completed
[2020-12-15 22:06:16.318][000][ID:001, Main]{APPL } | Closing app: Closed the IC crash handlers
[2020-12-15 22:06:16.323][004][ID:001, Main]{PFORM} | Shutdown end0 -
Found this one year old C1 post with a Win7 user getting a reply from C1 support that this problem was/(still is?) a known issue with Win7
Support's solution was to "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." (See second last post in that thread).
With support for W7 dropped that may be the only solution?
0 -
Thank you for the further info, gb. And the forum link regarding CO12 and same issue.
Yes, that is exactly the same thing as I do experience now with CO21. So maye the software engineers will fix this sometime, as they seemingly did with v12 in the end. Even though I never did have any problems with CO12 or CO20.
But nevertheless, I gave the possible cause with .NET Framework another try. Updated .NET 4.7 and 4.8. And installed CO21 afterwards. But issue still exists.
Locking at the log files there seem to be some hints of some problems. A complete list of the log files with the closing process, I have posted here:
https://www.dropbox.com/s/yd8h6gojgb0lilo/CO21_closing-Process_Log-files_2020-12-15_19-48.txt?dl=0The following lines caught my attention. But it is hard for me to tell and to know what to do.
Application.log [seems to be fine]
---------------------
…
[2020-12-15 19:48:09.042][185][ID:001, Main]{APPL } | Closing app: Closing OpenCore
[2020-12-15 19:48:09.042][000][ID:001, Main]{APPL } | Closing app: Closed OpenCore
[2020-12-15 19:48:09.042][000][ID:001, Main]{APPL } | Stopping IC
[2020-12-15 19:48:09.177][135][ID:001, Main]{APPL } | Cleaning up temporary files
[2020-12-15 19:48:09.179][002][ID:001, Main]{APPL } | Cleaning up temporary files in C:\Users\Admin-JH\AppData\Local\Temp\CaptureOneTemp1 ...
[2020-12-15 19:48:09.179][000][ID:001, Main]{APPL } | Temporary file clean up completed
[2020-12-15 19:48:09.179][000][ID:001, Main]{APPL } | Shutdown of managers and cores completed
[2020-12-15 19:48:09.181][002][ID:001, Main]{APPL } | Closing app: Closed the IC crash handlers
[2020-12-15 19:48:09.182][001][ID:001, Main]{PFORM} | Shutdown end
CaptureCore.log [Error noted]
----------------
…
2020-12-15 19:48:08.815 (7116 ) | CPS Provider - Terminated
2020-12-15 19:48:08.815 (7116 ) | Error: CaptureCore object leak detected. 15 objects not released.
2020-12-15 19:48:08.815 (7116 ) | Leaked objects with external references:
2020-12-15 19:48:08.815 (7116 ) | class CaptureOne::CaptureCore::Internal::BaseCaptureProviderList (1)
2020-12-15 19:48:08.815 (7116 ) | class CaptureOne::CaptureCore::Internal::CaptureCore (3)
2020-12-15 19:48:08.815 (7116 ) | class CaptureOne::CaptureCore::Internal::PTPCapture::CaptureProvider (2)
2020-12-15 19:48:08.815 (7116 ) | class CaptureOne::CaptureCore::EventReceiverNative (2)
2020-12-15 19:48:08.816 (7116 ) | class CaptureOne::CaptureCore::Internal::BaseEventSource::EventDispatcher (1)
2020-12-15 19:48:08.816 (7116 ) | class CaptureOne::CaptureCore::Internal::LightPhaseCapture::CaptureProvider (2)
2020-12-15 19:48:08.816 (7116 ) | class CaptureOne::CaptureCore::Internal::IQPCapture::CaptureProvider (2)
2020-12-15 19:48:08.816 (7116 ) | class CaptureOne::CaptureCore::Internal::CopyStandCapture::CopyStandProvider (1)
…ImgCore.log [Error at end?]
----------------
…2020-12-15 19:48:09.170> Shutting down: TileExecuter 0 [PYRAMID_PackageBitmapCPUProcessor0] (master: 14cc, worker: ce0)
2020-12-15 19:48:09.171> Shutting down: TileExecuter 0 [PYRAMID_PackageBitmapCPUProcessor0] (master: 14cc, worker: 13c8)
2020-12-15 19:48:09.171> Ending worker: TileExecuter 0 [PYRAMID_PackageBitmapCPUProcessor0] (master: 14cc, worker: 13c8)
2020-12-15 19:48:09.307> First chance exception (crash): 0xc00200010 -
No, don't think those errors are relevant as I get them too.
(although you do have more objects "not released").
Mine:
Error: CaptureCore object leak detected. 10 objects not released.
First chance exception (crash): 0xc00200010 -
Has anyone found a solution to this yet? I experience it as well. In addition, I'm getting hung up when ever I try to delete or move more than a file or two. Not sure if that's related.
0
Post is closed for comments.
Comments
19 comments