C1 8.1 hangs on export
I upgraded 8.02 to 8.1 under Windows 7 64bit
When now I export an image the TIFF gets exported but 8.1 freezes and I have to shut down via the Task Manager.
Reverting to 8.02 solved the problem.
Help would be welcome.
John
When now I export an image the TIFF gets exported but 8.1 freezes and I have to shut down via the Task Manager.
Reverting to 8.02 solved the problem.
Help would be welcome.
John
0
-
I've had exactly the same problem with every release of 8. Sometimes it falls over at the first export, sometimes I get though a few, but eventually - every time - the program locks up and I have to invoke Task Manager to recover.
Strangely, it works if I open Capture One in another user account, but to be honest I've given up with the palaver (and yes, I've worked with Phase One about this, to no useful effect), and just use converters (Photo Ninja, Lightroom 5, DxO Optics Pro 10) that work without having to jump through hoops.
Life's too short...0 -
Could memory leak be the reason (see one of the previous postst) ? If I look at Task Manager C1 consumes an enormous amount of RAM, plus there seems to be an instance of ImgCoreProcess running which also consumes a lot.
John0 -
[quote="NN262599UL" wrote:
Could memory leak be the reason (see one of the previous postst) ? If I look at Task Manager C1 consumes an enormous amount of RAM, plus there seems to be an instance of ImgCoreProcess running which also consumes a lot.
John
Bear in mind that processing to a TIFF file, presumably at 100% quality and size?, is likely to create a huge work file.
The last time I looked at this (using a different application, not C1) the TIFF work file was at least 8 times the size of the RAW file.
Grant0 -
I'd worry about any converter that can't cope with pushing out a full-sized tiff, Grant - 16 bit tiffs have been my output of choice for years, in every converter I use, and only Capture One has this problem: indeed, I frequently batch output hundreds of such files (usually in Lightroom, because it just works) without my machine so much as batting an eyelid.
I don't have a high-specced machine, either. And John has confirmed that for him, 8.02 is fine, so whatever has caused his issues, it came with 8.1.
John, I'm not convinced about memory leaks being the (entire) explanation: if it was, I'd expect that Capture One would fall over for me in the other User Account too (it's the same machine, after all); or for you in 8.02.
ImgCoreProcess is a necessary part of Capture One's processing, so again, if it was a problem, logically it'd be a problem for me in any User Account, and for you in 8.02.
Could you try running Capture One in a new User Account and see what happens?0 -
Keith,
It was more a comment about the IMGCoreProcess/memory relationship.
Using a lot of memory in a process is not, per se, a bad thing. No point in having it if it's not used.
Taking it and holding it if other processes need it is not so good.
Grant0 -
Hi Keith,
I re-installed 8.1, which is now building the catalogues again (I presume, with a CPU usage of 30% and a memory consumption of 1.6 GB). Apparently activity stopped with 0% CPU but still 1.4 GB. At the same time ImgCoreProcess is at 600 MB, without having to do something. This stuff is eating memory.....
I ran as a different user, and could not run ImgCoreProcess due to a socket error. I only managed to go up to 800 MB memory consumption, and despite the absence of Img... I could edit and save my images. Going back to my original account C1 had lowered to 570 MB and Img.. to 54 MB. Exporting one file brought this to 740 and 320 MB respectively at 0% CPU. Just clicking on a couple of images brings C1 up to 890 MB, withouot memory being freed at de-selection. I would say: memory problem.......
John0 -
Have you guys tried with disabled OpenCL support for processing? Just a hint. 0 -
[quote="NN262599UL" wrote:
memory problem...
Probably - but not a leak (as I understand the term, at least): the symptoms of a leak aren't what we're seeing here - leaks are more gradual, and build up over a period of time.
What's happening to us can happen on the first file being processed, which isn't "leaky", to my mind. There's no gradual depletion of available memory, which what a leak is, to my way of thinking.0 -
[quote="Paul_Steunebrink" wrote:
Have you guys tried with disabled OpenCL support for processing? Just a hint.
Yep. Doesn't help either way.0 -
I have the same issue. Installed 8.1 (not a clean install as I wanted to see it before removing 8.01.)
Windows 7 64bit system.
If I open C1 and first export a tiff it freezes. I decided to see if exporting jpegs worked. I successfully got two or three exported and then tried a tiff. Voila it worked. No hang. Was able to do several tiffs and raw files before it froze. I was monitoring the IMGCoreProcess file in task manager and noted the memory usage was over 400K-600K before attempting tiffs and got as high as 1000k. Over time the memory usage receeds. And C1 hangs. It seemed after quite a bit of messing around that the memory use in IMGCoreProcess had to be over about 400k for tiffs to work. Otherwise it froze.
This feels like a broken array/boundary issue. But really I haven't a clue.`Just hope this info helps the developers fix the problem with tiffs.0 -
FWIW I noticed that C1 V8 exit would leave the IMGCore process running (and in my case prevent opening another instance until it had been killed). Reported it a while back and have not seen a recurrence with 8.1 which seems to work just as expected in terms of opening and closing programs.
The pre 8.1 temporary fix was to turn off OpenCL processing (both) which on my machine was not active anyway sonce the GPU options are always rejected for lack of power according to the log file.
In fact OpenCL for display seemed to be the problem at the time. Leaving OpenCL on for output was not a problem when exiting C1 as far as IMGCore being orphaned was concerned.
Grant0
Post is closed for comments.
Comments
11 comments