Strange activity when exiting C1 20
Hi,
I have noticed that C1 20 can spend a lot of time writing to the disk when exiting. In one case, I got the Saving... message during 5 (five) minutes until it eventually definitively exited.
I have done some monitoring in order to understand what's happening. The following is what I observed [using WIndows 10]...
1. Just before clicking on the exit button, there's only one file in C:\Users\<user>\AppData\Local\Phase_One\CaptureOne.exe_StrongName_y3yh4brhpfi14u41fltdrpfruizxirsn\13.0.0.155 : user.config. When exiting, C1 spends a lot of time writing 2 files in this folder : xxxxxxxx.newcfg and yyyyyyyy.newcfg - x and y are placeholders; actual names will vary - (they do not exist when the quit command is issued). These files are no longer there when the program has definitively exited. So, I'm wondering what they are for. Maybe they are temporary files where information is gathered that will be later written to the logs.
2. C1 also spends some time writing to C:\ProgramData\Phase One\Capture One\Diagnostics\bc00abc7-0114-411e-814c-f6133c9a3639_1.p1report (or similar name) but at the end (once C1 has definitively existed), the Diagnostics folder remains empty (as it was when starting C1).
Depending on what has been done during the C1 session (session being meant in the general sense of the word, not the C1 sense), the Saving... process may last a rather long time or it can be almost instantaneous.
Never seen this before.
PS : This is not a catalog backup related activity. I have set the backup option to "never". So, what is it actually saving ?
I have noticed that C1 20 can spend a lot of time writing to the disk when exiting. In one case, I got the Saving... message during 5 (five) minutes until it eventually definitively exited.
I have done some monitoring in order to understand what's happening. The following is what I observed [using WIndows 10]...
1. Just before clicking on the exit button, there's only one file in C:\Users\<user>\AppData\Local\Phase_One\CaptureOne.exe_StrongName_y3yh4brhpfi14u41fltdrpfruizxirsn\13.0.0.155 : user.config. When exiting, C1 spends a lot of time writing 2 files in this folder : xxxxxxxx.newcfg and yyyyyyyy.newcfg - x and y are placeholders; actual names will vary - (they do not exist when the quit command is issued). These files are no longer there when the program has definitively exited. So, I'm wondering what they are for. Maybe they are temporary files where information is gathered that will be later written to the logs.
2. C1 also spends some time writing to C:\ProgramData\Phase One\Capture One\Diagnostics\bc00abc7-0114-411e-814c-f6133c9a3639_1.p1report (or similar name) but at the end (once C1 has definitively existed), the Diagnostics folder remains empty (as it was when starting C1).
Depending on what has been done during the C1 session (session being meant in the general sense of the word, not the C1 sense), the Saving... process may last a rather long time or it can be almost instantaneous.
Never seen this before.
PS : This is not a catalog backup related activity. I have set the backup option to "never". So, what is it actually saving ?
0
-
I see this too - not for five minutes, but enough to get my attention, and I've no idea what's going on, but it's new to me too. 0 -
It's happening to me as well. 0 -
I have had this problem a few times, when I get tired of waiting for Capture One to shut down I give it a 3 finger salute and kill the Capture One process. 👿
Other than a popup telling me I shut down incorrectly and will I tell Capture One what I was doing when shut down occurred I have seen no adverse effect from crashing out of the program.
Dave0 -
David532 wrote:
I have had this problem a few times, when I get tired of waiting for Capture One to shut down I give it a 3 finger salute and kill the Capture One process.
I did this once because C1 took too much time to exit and because the current catalog was a test catalog. I had to rebuild it afterwards. It didn't survive the process killing.0 -
have you guys exempt the c1 folders from the windows defender scans? wondering if it might have some impact
also all the c1 process as well and the c1 file extensions0 -
Samoreen wrote:
1. Just before clicking on the exit button, there's only one file in C:\Users\<user>\AppData\Local\Phase_One\CaptureOne.exe_StrongName_y3yh4brhpfi14u41fltdrpfruizxirsn\13.0.0.155 : user.config. When exiting, C1 spends a lot of time writing 2 files in this folder : xxxxxxxx.newcfg and yyyyyyyy.newcfg - x and y are placeholders; actual names will vary - (they do not exist when the quit command is issued). These files are no longer there when the program has definitively exited. So, I'm wondering what they are for. Maybe they are temporary files where information is gathered that will be later written to the logs.
More about this. Actually, the xxxxx/yyyyy.newcfg files are probably a temporary version of user.config. It seems that even when no or little change has been made to the C1 configuration, the whole configuration file is written back to disk in a temporary file and then copied to user.config. Since these files are XML files, I'm not sure that this is absolutely necessary. However, since C1 is a Microsoft .Net Framework app, this could be caused by an incorrect use of the configuration file API of the .Net Framework.0 -
I see the same problem. 5 minutes and longer. It is nearly so slow that I am considering no longer using CaptureOne! Totally unacceptable. But if, as you say, just killing the process takes care of things, then maybe that will be good enough. Love those automatic updates I am paying for!
0
投稿コメントは受け付けていません。
コメント
7件のコメント