15.4.0 not responding on close for up to 30 seconds
After the update to 15.4.0 version I frequently experience that it stops responding for 10 to 30 seconds when I click the main window close button. It seems to depend on number of opened photos during the session. My machine has 32 GB RAM, so it isn't hitting the hw limits and no crappy 3rd party antivirus installed. No such issues with previous versions.
EDIT: I am aware the version 23 is around the corner, but could you please fix it for the 22? Thanks.
-
Can confirm also having this issue. I thought the application had hung on exit but seems to be software. Never experienced this with the previous versions
Edit: as others have added some specs.
Win10 Enterprise
AMD TR 1920X
32GB ram
nv30901 -
Yes this is happening to me as well, but not every time.
2 -
I am having the same issue.
1 -
Das gleiche Problem habe ich ebenfalls nach dem Update auf 15.4. Nach dem Versuch das Programm zu schließen, dauert es jedes Mal die schon genannte halbe Minute. Vorher hatte ich nie Probleme.
1 -
I'm also seeing this behavior on my computer, but it's more like 10-15 seconds rather than 30 and doesn't happen consistently. However, there didn't seem to be any delay with 15.3 and earlier versions.
1 -
Same problem here.
1 -
This is happening to me to. I am also having problems copying adjustments layers. I get pending applying adjustments that never ends.
I installed Windows 11 and my pc crashed on start up of Capture one.I have 64gb ram
5950x
6950xtEvery few months there are Problems with this software....
Back on Windows 10 now, but same problem when shutting down and when copying adjustments layers.
1 -
Same issue for me on Windows 10. Take too long to close down since latest update.
1 -
Just happened to me after exporting 25 images as JPGs. Created a crashdump upon restarting Capture One which was submitted to Support. Hopefully it will give them the information necessary to fix this bug.
1 -
When I rename a file from
anna001 to Anna001 capture one hangs. (psd files).
Not a big deal but shouldn't happen.
0 -
> Joeri Peeters: ...from anna001 to Anna001
It may possibly confuse things that Windows filenames are generally not case sensitive; anna001 and Anna001 is the same filename. You could try a two step change from anna001 to nna001 and then from nna001 to Anna001.
0 -
Same here on Windows 10.
Some Times it takes longer than 30 sek. to shutdown C1.When i try to restart C1 a little while after that long Shutdown, the Warning that C1 is already running appears.
So some Kind off "C1-Job" is still running in the Background and C1 was not completely Shut down at all, although there was now Window oder Symbol to see in the Taskbar anymore.cu
Kurt
1 -
> Kurt Hõdl: C1 is already running appears...
It is not uncommon for applications to leave a process or more running to finish work without an active user interface part. You should be able force quit any leftover Capture One process(es) using the task list, but it may be a better idea to just let it finish.
0 -
Hi,
thx for answering..
For sure you can quit the Process useing the Taskmanager, but this is not the way how it should Work ;)..
And that the left over Process will shutdown by it selfe with some more Time than 30-60 sek.... may be, but this is not how C1 should to its work..And how the others commented before ...this behavior is new since the latest Release of C1.
cu
Kurt0 -
I have aditional another big problelm. When I copy adjustments from one photo to another. This takes forever, never enda. I have to shut down Capture one from task bar.
0 -
Yes same problem here.
0 -
> nameless user: I have aditional another big problelm
Knowing that your problem is different, you should consider starting a new thread of your own rather than hijacking a fellow user's thread.
0 -
Thanks for the fix.
0 -
Yes. Quick shutdown now for me too. Thanks.
0 -
Petr Vones & Clive Blair: Which comment are you responding to? What was the fix for a quick shutdown?
Thanks
0 -
15.4.1 fixes it.
0 -
Robert: The latest update fixed the slow shutdown for me.
0
Please sign in to leave a comment.
Comments
22 comments