Capture One Freezing - Again
Hello,
I am curious if anyone else is having problems with Capture One freezing on them?
Iam running 9.0.3 and last night I was attampting to edit an image when Capture One froze on me and the only way to shut it down was to use the Task Manager in Windows 10.
I then opened another catalogue and verified the catalogue that had frozen to be told that it was faulty.
I repaired it, opened it and it froze on me.
I then replaced the main files with the ones in my backup and Capture One opened and worked alright, for a short time, and then froze again.
Capture One still opens the catalogue that I have problems with but freezes before all the images are loaded.
This is very frustrating as I have had this problem (on nad off) for almost a year now.
I've even bought a new computer and upgraded the RAM but it hasn't helped.
I'm even contemplating switching over to an iMac but can't afford the expense of doing so and shouldn't have to!
I'm paying monthly for an application that freezes on me and think I should get a large discount.
I have never had any problems with Lightroom or Photoshop, only Capture One!
I am curious if anyone else is having problems with Capture One freezing on them?
Iam running 9.0.3 and last night I was attampting to edit an image when Capture One froze on me and the only way to shut it down was to use the Task Manager in Windows 10.
I then opened another catalogue and verified the catalogue that had frozen to be told that it was faulty.
I repaired it, opened it and it froze on me.
I then replaced the main files with the ones in my backup and Capture One opened and worked alright, for a short time, and then froze again.
Capture One still opens the catalogue that I have problems with but freezes before all the images are loaded.
This is very frustrating as I have had this problem (on nad off) for almost a year now.
I've even bought a new computer and upgraded the RAM but it hasn't helped.
I'm even contemplating switching over to an iMac but can't afford the expense of doing so and shouldn't have to!
I'm paying monthly for an application that freezes on me and think I should get a large discount.
I have never had any problems with Lightroom or Photoshop, only Capture One!
0
-
Beo,
I did look at the Log Files etc. but they made no sense to me, I'm not skilled enough in 'computer skpeak' to know if something was right or wrong.
Grant,
I bought a completely new desktop computer as my old laptop wasn't quite up to the job of handling Capture One, too low spec.
I keep a seperate catalogue for each year (2008, 2009 etc.) and at the moment I can open all other catalogues but it's the 2016 catalogue that is causing me problems. That's not to say that my other catalogues haven't had problems, they have had the same problem of freezing \ hanging but nothing too serious, I've always managed to fix them through the Verify Catalogue feature.
It's quite odd that with my 2016 catalogue it will open one day and work perfectly but then when I open it again later that day it might freeze \ hang again; the next day it might freeze \ hang all day and I can't use it but the next day it'll open correctly but then later on freeze \ hang again... there's no pattern to it, nothing on my computer changes between opening the catalogue.
I've (just now) opened the 2016 catalogue and it's frozen \ hung again; only one out of 244 images has loaded into the browser window but that one image can be edited and I can still access all of the tabs such as Colour and Exposure etc.
If I now go to File> Exit the browser window dissappears and Capture One is still there, it won't close unless I use the Windows 10 Task Manager to make it shut down.
So the really frustrating thing is that there's no pattern to my problem, one minute Capture One will work, the next it won't but I never know when that might be.
Richard0 -
[quote="BeO" wrote:
[quote="Peter" wrote:
Would any sane person volunteer for v9.04?
Yes, me. (though not everyone would say I'm sane, but for other reasons... 😂 )
Me too.
Heck, I'd even volunteer for 9.1!
😂0 -
Despite (and probably because of) my problems I would jump at the opportunity to as the upgrade would bring in new feature and improve on some old ones, not to mention making Capture One work for me... 😉
Bring on V10
Richard0 -
Richard,
let's hope support will see your case soon and is able to help you with the information you've provided to them.
On my Windows 7 I occasionally observe that although the C1 window disappears on closing C1, the process is still there. Killing with task manager never caused any bad effect, as far as I can tell.
I'm shooting in the dark, but have you tried to disable OPENCL to see if that's maybe causing the issues? From the forum I have the impression OPENCL is in the top list when it comes to issues, though mainly with issues in the preview or output, who knows what else it can cause...
cheers
BeO0 -
[quote="BeO" wrote:
Richard,
let's hope support will see your case soon and is able to help you with the information you've provided to them.
On my Windows 7 I occasionally observe that although the C1 window disappears on closing C1, the process is still there. Killing with task manager never caused any bad effect, as far as I can tell.
I'm shooting in the dark, but have you tried to disable OPENCL to see if that's maybe causing the issues? From the forum I have the impression OPENCL is in the top list when it comes to issues, though mainly with issues in the preview or output, who knows what else it can cause...
cheers
BeO
I think it may take a little time to tidy up. A few seconds if using sessions with V7 Win.
Back in V8 times for a while I sometime had situations where C1 did not close all of its processes on exit but that was resolved by something - C1 or Windows, not sure which - in mid life.
OpenCL is a good candidate for analysis as it is accessible. My experience with my lowly GPU in V9 is that it does now work (it was always rejected previously) and, after a driver update and some playing around with settings in order to try to understand what things may affect performance, it seems to be working. That said it's not fast enough to set the machine alight and I don't think I can see it's activity other than by a GPU monitoring gadget, but it does seem to be working and reliably. That said I did go to the Manufacturer web site to get the driver as Windows was not reporting a possible update.
Grant0 -
I did try OpenCL once but it didn't work so I've not used it since, it's turned off within Capture One 9. 0 -
[quote="BeO" wrote:
Richard,
let's hope support will see your case soon and is able to help you with the information you've provided to them.
On my Windows 7 I occasionally observe that although the C1 window disappears on closing C1, the process is still there. Killing with task manager never caused any bad effect, as far as I can tell.
I'm shooting in the dark, but have you tried to disable OPENCL to see if that's maybe causing the issues? From the forum I have the impression OPENCL is in the top list when it comes to issues, though mainly with issues in the preview or output, who knows what else it can cause...
cheers
BeO
I know that some see disabling OpenCL as a miracle-cure for every problem, however, that is not so. Hang during startups can never be caused by OpenCL, because of the way it is implemented on seperate threads.0 -
[quote="Christian Gruner" wrote:
[quote="BeO" wrote:
Richard,
let's hope support will see your case soon and is able to help you with the information you've provided to them.
On my Windows 7 I occasionally observe that although the C1 window disappears on closing C1, the process is still there. Killing with task manager never caused any bad effect, as far as I can tell.
I'm shooting in the dark, but have you tried to disable OPENCL to see if that's maybe causing the issues? From the forum I have the impression OPENCL is in the top list when it comes to issues, though mainly with issues in the preview or output, who knows what else it can cause...
cheers
BeO
I know that some see disabling OpenCL as a miracle-cure for every problem, however, that is not so. Hang during startups can never be caused by OpenCL, because of the way it is implemented on seperate threads.
Christian,
I'm confused by your answer; are you saying that even though OpenCL is disabled within Capture One that it can still be causing my problem?
If that's so then what should I be doing about it?
Richard0 -
[quote="Richard_Allen" wrote:
[quote="Christian Gruner" wrote:
[quote="BeO" wrote:
Richard,
let's hope support will see your case soon and is able to help you with the information you've provided to them.
On my Windows 7 I occasionally observe that although the C1 window disappears on closing C1, the process is still there. Killing with task manager never caused any bad effect, as far as I can tell.
I'm shooting in the dark, but have you tried to disable OPENCL to see if that's maybe causing the issues? From the forum I have the impression OPENCL is in the top list when it comes to issues, though mainly with issues in the preview or output, who knows what else it can cause...
cheers
BeO
I know that some see disabling OpenCL as a miracle-cure for every problem, however, that is not so. Hang during startups can never be caused by OpenCL, because of the way it is implemented on seperate threads.
Christian,
Iconfused by your answer; are you saying that even though OpenCL is disabled within Capture One that it can still be causing my problem?
If that's so then what should I be doing about it?
Richard
Richard,
No I think Christian is saying that a hang that is purely related to starting C1 is not going to be caused by OpenCL.
The only reference to OpenCL during initial start up is to discover any devices on the system that can run OpenCL and assess their performance.
Once up and running and into processing stuff OpenCL may become a factor (although these days is seems pretty much under control in terms of the maturity of graphics cards and drivers) but as it works on multiple channels is would not directly cause a "hang" or crash. The results of OpenCL issues, if they occur, are more usually poor or corrupted outputs. I would guess there is some potential for issue in the processing pipe that might screw things up and crash the system in some circumstances but a Hang would have some other cause - especially during the startup phase.
Or at least that would be my interpretation.
Grant0 -
Grant,
Thank you for that, it's just that having OpenCL mentioned jogged my memoory with regards to my problem...
Capture one was working as it should do, I then read about using OpenCL and thought it might improve performance so I enabled OpenCL through Capture One.
I can't remember exactly what happened after enabling it but it caused some sort of problem (for the life of me I can't remember what) so I disabled it.
It was after that that I started to have problems with Capture One hanging so I'm wondering if just by the fact of enabling and then disabling OpenCL I've inadvertently now got this problem?
Just a thought.
But then if that is the cause then that would (I think) imply that there was indeed a problem with Capture One?
Regards,
Richard0 -
[quote="SFA" wrote:
Or at least that would be my interpretation.
Grant
Correct 😊0 -
[quote="Richard_Allen" wrote:
Grant,
Thank you for that, it's just that having OpenCL mentioned jogged my memoory with regards to my problem...
Capture one was working as it should do, I then read about using OpenCL and thought it might improve performance so I enabled OpenCL through Capture One.
I can't remember exactly what happened after enabling it but it caused some sort of problem (for the life of me I can't remember what) so I disabled it.
It was after that that I started to have problems with Capture One hanging so I'm wondering if just by the fact of enabling and then disabling OpenCL I've inadvertently now got this problem?
Just a thought.
But then if that is the cause then that would (I think) imply that there was indeed a problem with Capture One?
Regards,
Richard
if CO doesn't start, it is quite safe to say there was a problem. But as CO related on so many external factors, both software and hardware, it will be quite hard to do a post-mortem on it, now that it is actually working.
Rest assured that we have a lot of focus on stability, and we continuously investigate solutions to further increase it.0 -
Thank you Christian and Grant; once again you've been very helpful... 😊 0 -
[quote="Christian Gruner" wrote:
[quote="Richard_Allen" wrote:
Grant,
Thank you for that, it's just that having OpenCL mentioned jogged my memoory with regards to my problem...
Capture one was working as it should do, I then read about using OpenCL and thought it might improve performance so I enabled OpenCL through Capture One.
I can't remember exactly what happened after enabling it but it caused some sort of problem (for the life of me I can't remember what) so I disabled it.
It was after that that I started to have problems with Capture One hanging so I'm wondering if just by the fact of enabling and then disabling OpenCL I've inadvertently now got this problem?
Just a thought.
But then if that is the cause then that would (I think) imply that there was indeed a problem with Capture One?
Regards,
Richard
if CO doesn't start, it is quite safe to say there was a problem. But as CO related on so many external factors, both software and hardware, it will be quite hard to do a post-mortem on it, now that it is actually working.
Rest assured that we have a lot of focus on stability, and we continuously investigate solutions to further increase it.
"now that it is actually working"... Capture One isn't working for me as it should, I'm still having the same problem?
Regards,
Richard0 -
Richard,
It depends. Remember that correlation is not causation - especially when we are basing it on a memory of events rather than a recorded audit trail - like a log file if it is a complete enough record!
what puzzled me it that, as I recall for your comments, you have had problems with catalogues last year. Now you have a new catalogue and that too has problems after relatively little use (200+ files?) Yet some of the older catalogs are working fine, so far as you can tell. And even the current problem catalogue can, sometimes, be OK for a few days at a time.
Furthermore IF a problem arises when you open a catalogue it may occur almost immediately or it may be some time into working with the catalogue open before the problem occurs. Is that correct?
When you get a freeze can you still use Windows Explorer independently and all other applications you have running still work as normal?
If you open the catalogue and just scroll through the ALL images using the browser and no filters - right arrow, right arrow, etc. giving time for the preview to display - do you get any problems? As you do that do you see any images that look "corrupt" - areas that have blocks with streaks of colour or just black ... that sort of thing.
Finally, for now, I can't recall if you have a cloud based file sharing service set up. If you have would you be happy to share the log files so I can pop them into my analysis development project and see what comes out. Very basic stuff at the moment - it's a matter of working through whet there is to see what is possibly meaningful and what can safely be passed over. I'm looking for data related matters rather than technical process related on the basis that the technical stuff, where reported, is already known - which is not the case, it seems, with your problem.
Grant0 -
[quote="SFA" wrote:
Richard,
It depends. Remember that correlation is not causation - especially when we are basing it on a memory of events rather than a recorded audit trail - like a log file if it is a complete enough record!
what puzzled me it that, as I recall for your comments, you have had problems with catalogues last year. Now you have a new catalogue and that too has problems after relatively little use (200+ files?) Yet some of the older catalogs are working fine, so far as you can tell. And even the current problem catalogue can, sometimes, be OK for a few days at a time.
I did have the exact same problem last year and it's caused problems (on and off) since then. So you are correct in that most of the time when attempting to open my 2016 catalogue it isn't opening correctly but previous catalogues are (most of the time). I attempted so many different things such as copying my backup files into the current catalogues to see if that helped (somtimes it did but not for long) that I've lost track of everything I did.
Furthermore IF a problem arises when you open a catalogue it may occur almost immediately or it may be some time into working with the catalogue open before the problem occurs. Is that correct?
99% of the time the offending catalogue will freeze on opening but somtimes it will open correctly and then freeze after quite some time. The other day it opened correctly all day long and only froze when attempting to open it the following day.
When you get a freeze can you still use Windows Explorer independently and all other applications you have running still work as normal?
When Capture One freezes I can still use Windows Explorer and any other application I choose without them having a problem; Capture One freezing doesn't affect anything else.
If you open the catalogue and just scroll through the ALL images using the browser and no filters - right arrow, right arrow, etc. giving time for the preview to display - do you get any problems? As you do that do you see any images that look "corrupt" - areas that have blocks with streaks of colour or just black ... that sort of thing.
I've just opened my 2016 catalogue (the one giving me problems) and it loaded 133 of 244 images (sometime this can be just 1 of 244 images -see here http://supportcasefiles.phaseone.com/51 ... %20III.jpg I scrolled through all of the 133 images showing in the browser window and none of them are showing any signs of being corrupt although it has happened a few times recently with a distinct band running through an image, one half of an image showing as un-processed, the other half showing as processed.)
Finally, for now, I can't recall if you have a cloud based file sharing service set up. If you have would you be happy to share the log files so I can pop them into my analysis development project and see what comes out. Very basic stuff at the moment - it's a matter of working through whet there is to see what is possibly meaningful and what can safely be passed over. I'm looking for data related matters rather than technical process related on the basis that the technical stuff, where reported, is already known - which is not the case, it seems, with your problem.
I have uploaded the Log files to Google Drive and they can be accessed here https://drive.google.com/folderview?id= ... sp=sharing
I tried uploading the files one by one but Google didn't want to 'play ball' so I ended up uploading the files as a.rar file, sorry...
Regards,
Richard
0 -
Richard,
Is that image that appears in the browser area of your jpg screen shot cropped?
It has a dark strip across the top. I don't want to read to much in a screen grab but the top line of the image looks slightly jagged. Does it also display like that on screen when viewing?
Grant0 -
Grant,
That image has been cropped along the top, hense the dark strip you can see.
When viewed the jagged edge only shows in the browser window and not in the main window.
It's to do with a slight rotation of the image to correct the horizon.
Richard0 -
Thanks Richard.
I assumed as much but it's always worth checking.
I'm still looking for patterns in the logs.
Does your catalogue have a mix of images stored internally, externally and, perhaps?, in the cloud?
Grant0 -
Grant,
My C: drive is an SSD whist I also have an internal HDD (E:) which houses all of my images and Capture One files.
Richard0 -
Whenever the hang occurs, create a memory dump from the Windows Task Manager (right click the Capture One application, and select "Create dump file", zip/rar it) and send it to Support. They will forward it to R&D for further analysis.
I took a look at your log-files and found a few interesting things (for a tester, that is), which I will dig into next week.0 -
[quote="Christian Gruner" wrote:
I took a look at your log-files and found a few interesting things (for a tester, that is), which I will dig into next week.
There are a few interesting things for a non-tester as well Christian!
That said I think my own session based logs are even more interesting (and larger) - but I don't have the problems .... 😕
Grant0 -
[quote="Christian Gruner" wrote:
Whenever the hang occurs, create a memory dump from the Windows Task Manager (right click the Capture One application, and select "Create dump file", zip/rar it) and send it to Support. They will forward it to R&D for further analysis.
I took a look at your log-files and found a few interesting things (for a tester, that is), which I will dig into next week.
Christian,
I've already sent Support three Dump Files and Crash Reporter Files.
I must say how much I am pleased by your and Grants help in this matter, it restores my faith in human kind... 😄
Regards,
Richard0 -
[quote="Richard_Allen" wrote:
Grant,
My C: drive is an SSD whist I also have an internal HDD (E:) which houses all of my images and Capture One files.
Richard
Richard,
Is your 2016a catalogue a duplicate in some way? Or do you have 2 copies of it, one on C: and the other on E: ?
Also, If I read things correctly, you have multiple Collections in the catalogue based on date.
If you work with one of those collections rather than All (perhaps you already do?) will they all exhibit the problems or do some of them seem to work without problems?
I can undertake a lot of extraction and grouping from the reported log lines but whether any of it is meaningful may depend on an understanding of how you are working with the images in collections.
I also see a lot of Initiations for C1, what looks like a typical load and then nothing until it is "Userclosing" after a short period of nothing being logged. I'm not yet sure whether that correlates with your "Freeze" situation. Crashes are evident (though reasons may not be obvious yet) but "Userclosing" with little or no apparent activity is a bit more of a puzzle - unless you were repeatedly testing what happened - a perfectly valid thing to do of course.
Grant0 -
[quote="SFA" wrote:
[quote="Richard_Allen" wrote:
Grant,
My C: drive is an SSD whist I also have an internal HDD (E:) which houses all of my images and Capture One files.
Richard
Richard,
Is your 2016a catalogue a duplicate in some way? Or do you have 2 copies of it, one on C: and the other on E: ?
Because I was having problems with my 2016 catalogue I created another catalogue and called it 2016a; I then imported my latest original (not imported from Capture one but directly from where the original images are stored) images into it and processed them as I had done to ones in the origianl 2016 catalogue. This was to see if creating a new catalogue of the same images resulted in the same problem. I was attempting to see if I could circumvent what was causing my problem. I then deleted the original 2016 catalogue and re-named the 2016a catalogue as 2016 (did that make sense?).
Also, If I read things correctly, you have multiple Collections in the catalogue based on date.
That's correct, I have sequential catalogues, 2008, 2009 all the way to 2016.
If you work with one of those collections rather than All (perhaps you already do?) will they all exhibit the problems or do some of them seem to work without problems?
None of my other catalogues are exibiting the same behaviour as the 2016 catalogue, one reason why I thought I'd create the 2016a one.
I can undertake a lot of extraction and grouping from the reported log lines but whether any of it is meaningful may depend on an understanding of how you are working with the images in collections.
I also see a lot of Initiations for C1, what looks like a typical load and then nothing until it is "Userclosing" after a short period of nothing being logged. I'm not yet sure whether that correlates with your "Freeze" situation. Crashes are evident (though reasons may not be obvious yet) but "Userclosing" with little or no apparent activity is a bit more of a puzzle - unless you were repeatedly testing what happened - a perfectly valid thing to do of course.
I'm not used to the term 'Userclosing' and would imaging it correlates with having to use the Windows Task Manager to close Capture One as it was the only way I could achieve this. From time to time I would start Capture One to see if it was going to load correctly but as soon as I saw it had frozen I had to use the Task Manager to close it.
One last thought; I keep all of my original images in the Google Drive folder on the HDD (E:) so that they are automatically backed up to the cloud. Could the fact that these images are within that folder be causing problems. I don't see why as Capture One should only be reading from the Adjustments folder, or so I assume?
Grant0 -
Richard,
you have a "Write access violation" in imgcore.log, and "Could not enter WriteLock lock" and "Deadlock" messages in the application log.
I am not familiar with google drive but I would recommend to not use it for Capture One just to verify or falsify that this is somehow causing the hangs and exceptions.
"XMP Sync is set to : Load"
Do you need this?
Cheers
BeO
btw, Capture One of course writes into the Adjustments folder.0 -
A long shot Richard but when things are no obvious - heck, why not?
Your internal E: drive doesn't by any chance have an Eco energy saving mode does it?
I ask because I have an EXTERNAL drive that, when I use it, has a habit of going into some sort of hibernation and if I happen to be using the wrong USB3 cable (another mystery) more often than not does not wake up "on demand".
Using a shorter cable it is not a problem - but that's another matter.
The time when you have seemingly got bored with waiting (not unreasonable) and killed the process (which shuts things down happily as far as C1 reports) seem like they may coincide with starts that could be struggling to access the files they have been tasked to open. I'm speculating at the moment but knowing if such a thing might be a possibility could save a lot of time. (Or, on the other hand, it might create some chasing after wild geese ....)
Grant0 -
My assumption is that google synchronisation on the E drive might possibly interfer with some locks on C1 files. Could be wrong but I personally would try to take this out of the equation. 0 -
[quote="BeO" wrote:
My assumption is that google synchronisation on the E drive might possibly interfer with some locks on C1 files. Could be wrong but I personally would try to take this out of the equation.
Could be but there are more situations where it looks like Richard has elected to kill off a perceived "freeze" than I have so far seen for the Lock problem reports.
You know it would be really good to have somewhere to take this discussion off-line while we are floundering around trying to interpret things until Christian comes back and tells us we guessed wrong!
😉
Grant0 -
I think you're too far away from me for a beer in a pub 😕 😂 0
Post ist für Kommentare geschlossen.
Kommentare
83 Kommentare