CO 7.1.1 has been importing for 36 hours
And is only on image 13292 of 15203.
Now, this is better than before, when it would get to image ~8k of 15203 and crash (7.1), but is still "sub-optimal".
the conversion rate has gone from tens-per-second to now one per minute. Over the past 24 hours it has dropped from 1 imported image every 3 seconds to one image every 55 seconds.
It seems to be spending a lot of time in this:
I'm willing to let it run for another 36 hours (which, at this rate, is what it'll take), but this is a bit silly.
Now, this is better than before, when it would get to image ~8k of 15203 and crash (7.1), but is still "sub-optimal".
the conversion rate has gone from tens-per-second to now one per minute. Over the past 24 hours it has dropped from 1 imported image every 3 seconds to one image every 55 seconds.
It seems to be spending a lot of time in this:
+ ! : | + ! 1148 _dispatch_client_callout (in libdispatch.dylib) + 8 [0x7fff947750b6]
+ ! : | + ! 1148 __38-[ObjectContext _performOnCacheQueue:]_block_invoke_0 (in Capture One) + 111 [0x10027bdf2]
+ ! : | + ! 771 -[ObjectContext _addToObjectCacheOnCacheQueue:] (in Capture One) + 365 [0x10027ba66]
+ ! : | + ! : 382 -[_ObjectKeyQueue removeOldestObject] (in Capture One) + 92 [0x10026f022]
+ ! : | + ! : | 365 -[__NSDictionaryM objectForKey:] (in CoreFoundation) + 142 [0x7fff967ac16e]
+ ! : | + ! : | + 282 -[__NSCFNumber isEqual:] (in CoreFoundation) + 70 [0x7fff966be9e6]
+ ! : | + ! : | + ! 263 -[__NSCFNumber isEqualToNumber:] (in CoreFoundation) + 24 [0x7fff966bea18]
I'm willing to let it run for another 36 hours (which, at this rate, is what it'll take), but this is a bit silly.
0
-
Size of your previews, amount of RAM, OS X, GPU, amount of free RAM: to mention some parameters that affects performance and might be interesting to share.
I mean, not mention any parameter is a bit silly too (no offense).0 -
Good point, sorry:
2.6GHz Core i7 (4 core, HT [8 'cores'])
OS X 10.8.3
16GB RAM, 5.83GB "inactive", 487MB "free", (it was this slow even when the free size was 4GB)
NVIDIA GeForce GT 650M 1024 MB
CaptureOne is using 2.30GB of RAM and 100% of a single core (though obviously, the load moves from core to core). That load hasn't changed since the beginning, but the relative "processing" speed has gotten lower and lower, even when capture one is the only thing running. (in addition, the other 3 cores are only at ~12-25% load). So whatever's going on, it's only going on in one thread, and it's not using much memory to do it. Previews are full size.
Thinking it was a catalog problem, I cleared it out in CO6 and rebuilt it, which (building and making full-size previews) took under 40 minutes on the same computer.0 -
Well, after 52 hours, it finally crashed. It was on image 14402 of 15203 when last I checked on it.
Then the error reporter crashed as I was adding content.0 -
My computer has done the EXACT same thing as yours on EVERY new version of C1-7. I've tried fresh installs, referenced vs managed, different hard drives with terabytes to spare. All of this on mountain lion with a hexacore 3.33 ghz Xeon, 16gb ram, ssd drive for os, quadro 4000 for the Mac, and a partridge in a pear tree!
Sorry phase one, the problem is with your coding - not out machines.
I'm sticking with Lightroom and I hate Lightroom until your product works properly. Importing is a very basic function. Btw, I can import my entire library to Lightroom and aperture with no hiccups.0 -
I must Say that importing is a major problem, and a very basic one. I for one have opened a case, sent all the file as required, done this and that. Cancelled old catalogs, session what ever..... But it still crashes upon importing more than a few files.......I am relay stunned.... Because the look and fell of the images is great and I do want it to work well.... But if I can't import what good does it do to me?
Alessandro0 -
We do test with many thousands of files before releasing the software, and don't see those crashes ☹️
If you haven't done it already, please create a support case, so we can be rid of this annoying crash.
Be sure to include system profile, log files and crash reports.0 -
How about doing it with 50k files and get back to us? Otherwise like the previous poster said, you're eastong our time. 0 -
[quote="Christian Gr" wrote:
We do test with many thousands of files before releasing the software, and don't see those crashes ☹️
If you haven't done it already, please create a support case, so we can be rid of this annoying crash.
Be sure to include system profile, log files and crash reports.
I have opened a case, send all my archive logs and waiting for an answer since it is the easter holidays....0 -
[quote="Christian Gr" wrote:
We do test with many thousands of files before releasing the software, and don't see those crashes ☹️
If you haven't done it already, please create a support case, so we can be rid of this annoying crash.
Be sure to include system profile, log files and crash reports.
I have filed a report. As a side note, the "upload file" dialog (on mac, in Chrome) would not allow me to upload non-image files (such as 'log.txt').0 -
[quote="NN892931" wrote:
[quote="Christian Gr" wrote:
We do test with many thousands of files before releasing the software, and don't see those crashes ☹️
If you haven't done it already, please create a support case, so we can be rid of this annoying crash.
Be sure to include system profile, log files and crash reports.
I have filed a report. As a side note, the "upload file" dialog (on mac, in Chrome) would not allow me to upload non-image files (such as 'log.txt').
Tip: zip files before upload0 -
If I had to guess, just shot-in-the-dark style, I'd suspect it was some problem with SQLite. I need to see if the cocatalog file is corrupt, or if I can look at it to see what the tables are like, but my guess is that as the rowcount goes up, the insertion time gets longer and longer and longer until it finally dies. Which would be an especially bad problem because it's not actually PhaseOne's fault, in a way. 0 -
[quote="Paul_Steunebrink" wrote:
[quote="NN892931" wrote:
[quote="Christian Gr" wrote:
We do test with many thousands of files before releasing the software, and don't see those crashes ☹️
If you haven't done it already, please create a support case, so we can be rid of this annoying crash.
Be sure to include system profile, log files and crash reports.
I have filed a report. As a side note, the "upload file" dialog (on mac, in Chrome) would not allow me to upload non-image files (such as 'log.txt').
Tip: zip files before upload
Oh they have been ziped alright..... that is not the problem0
Post is closed for comments.
Comments
12 comments