Observations concering crashes
Hi,
sadly Ulf's post is locked because I'd like to add some informations and observations concerning crashes and errors.
1) It seems that it mostly happens with files which have more complex adjustments and edits, like adjustment layers, spot removal, selective colour enhancements etc.
2) Such crashes/errors seem to happen when advancing quickly from one image (with complex adjustments) to the next. It seems that the time may be insufficient for the progam to read the adjustment file / create the visualization. Or in other words, this reading / creation of the visualization is interrupted too early when one skips quickly to the next file. However when browsing slower through the files the problem doesn't happen.
3) There seem to be a relation to the working environment whether one is working on files stored on the computers harddisc or on files stored on an external drive.
4) In the most sticky cases I had to delete the preview and adjustment files (deleting the whole C1 folder) to return to normal working conditions. In some of those situations I copied the adjustment info files temporarily to another folder and later back so no need to redo the adjustments.
5) I suspect some relation to the version, i.e. (complex) adjustments created in V7.1.1 seem to crash in V7.1.3. But no hard data for this since I have no tracks about which files were edited (first / last / actually) in which version.
Hope this provides some help for narrowing done the search.
sadly Ulf's post is locked because I'd like to add some informations and observations concerning crashes and errors.
1) It seems that it mostly happens with files which have more complex adjustments and edits, like adjustment layers, spot removal, selective colour enhancements etc.
2) Such crashes/errors seem to happen when advancing quickly from one image (with complex adjustments) to the next. It seems that the time may be insufficient for the progam to read the adjustment file / create the visualization. Or in other words, this reading / creation of the visualization is interrupted too early when one skips quickly to the next file. However when browsing slower through the files the problem doesn't happen.
3) There seem to be a relation to the working environment whether one is working on files stored on the computers harddisc or on files stored on an external drive.
4) In the most sticky cases I had to delete the preview and adjustment files (deleting the whole C1 folder) to return to normal working conditions. In some of those situations I copied the adjustment info files temporarily to another folder and later back so no need to redo the adjustments.
5) I suspect some relation to the version, i.e. (complex) adjustments created in V7.1.1 seem to crash in V7.1.3. But no hard data for this since I have no tracks about which files were edited (first / last / actually) in which version.
Hope this provides some help for narrowing done the search.
0
-
I think a Support Case would be your best bet.
Some of what you described just sounds like Memory shortages and we can easily confirm or rule out this possibility with software logs and crash reports.0 -
Hi,
sorry but with 16GB of RAM and 3GB of memory on the graphics card memory (GeForce GTX 670MX) capacity shouldn't be a problem.0 -
[quote="Drew" wrote:
I think a Support Case would be your best bet.
Some of what you described just sounds like Memory shortages and we can easily confirm or rule out this possibility with software logs and crash reports.
Hi,
I work only with session. My computer, Intel I7 3770, 32GB RAM, SSD for software, Raid 1 on two HDD 3TB, Graphic card Nvidia 770.
I met like Michael second item : 2) Such crashes/errors seem to happen when advancing quickly from one image (with complex adjustments) to the next. It seems that the time may be insufficient for the progam to read the adjustment file / create the visualization. Or in other words, this reading / creation of the visualization is interrupted too early when one skips quickly to the next file. However when browsing slower through the files the problem doesn't happen.
I submitted the case to the Phase One support. I made a lot of reinstallation without effect. I sent logs files. They concluded that it is not a problem with C1 but with files and Windows.
Ok, I rebuilt my computer, very clean with new Windows, new software installation. I changed my graphic card (previous Nvidia quadro 600).
Today, always the same problem. 👿 👿 👿
I think you will make a lot of progress if you listen the users, even if you don't find immediatly the solution. It is better to say, "sorry, today we don't understand why, but we study your cases." than "it is your Windows installation".
I lost one week to rebuilt it.
Regards.0 -
Hi,
exactly. What I found particulary intriguing is that when I imagine "browsing" through images (even if they have complex adjustments) should be a "reading process". So if time was too short for reading and interpretation of the adjustment parametres then the visualization wouldn't show to image correctly (during the short instance until the jump to the next image; not to forget "browsing"). That would be absolutely fine. However, I don't get it why this reading-only process would be able to corrupt the data-set (or worse: several of data-sets). In addition, this would mean some writing process - and this should be performed by C1, or not? Why would Windows or any other OS mess around with application specific files?
Just thinking a bit further: if a read data-set (i.e. transferred into RAM) gets corrupted by some unknown process or reason, ok. Then C1 might run into an error and a restart may be necessary. But this still wouldn't explain why the data-set stored on the HD gets corrupted.0 -
[quote="Michael11" wrote:
Michael provided a very detailed post .....
FWIW ...
I had a bad session some time back that would freeze and/or die when simply progressing through the browser previews.
Every time I took some action to 'fix' a problem at one place in the browse it came back some frames later.
Eventually, many files distant from where I was seeing problems, I spotted a very poor (eg. 50% failed) preview file that persisted evebn afted I had recreated previews.
On a hunch I deleted the edit file for that image. Magically all the problems disappeared and I could easily and speedily browse through the session once more. Recreating an .cos file still left the session operational.
This has only happened to me once. A single file in a single session causing a problem. I suspect a badly written .cos file - no idea why but these things happen form time to time.
It would be worth checking. Bear in mind we ar working with a database here and the internal workings may not have any logical representation in the way the problems are presented to us. My folder had something like 2000 images and, displayed to me in file name order, the problem image was nowhere near the the images with which I was having problems. There is no reason why there should be any human/user understandable logical connection.
If you have something similar there may be a similar cause. It would be worth investigating, Until the problem edit file was identified and eradicated I had a number of seemingly random problems. Since then, no problems.
HTH.
Grant Perkins0 -
[quote="Photocor" wrote:
I submitted the case to the Phase One support. I made a lot of reinstallation without effect. I sent logs files. They concluded that it is not a problem with C1 but with files and Windows.
Interesting thread. I'm not sure how you can blame Windows when Mac users are experiencing the exact same issues you describe. We have encountered problems ever since loading C17.
We purchased 2 new Mac Pros with 12GB of ram and a clean install of the OS 10.8.4 and C1 7.1.3 to try and alleviate the problem at great expense but to no avail.
We shoot tethered with a Nikon D3X and nikon D800 and encounter multiple crashes daily. Very annoying when you have a client on the set looking over your shoulder!
They seem to be pointing to the tethering or camera in this case. Now they want me to see if I can make it fail untethered. We seem to be their Guinea pigs.
I'll keep you updated although it seems to be a widespread C17 issue on all platforms, so it will be up to phase one to make the fix.
We have an open support case.0 -
[quote="Steve Mac" wrote:
Interesting thread. I'm not sure how you can blame Windows when Mac users are experiencing the exact same issues you describe. We have encountered problems ever since loading C17.
..........
We have an open support case.
Excuse me but my English is bad, I think there is a little misunderstanding: I blame C1, not Windows because I reinstalled it and softwares.
I deleted files with extension .cos.error. without benefits.
I have also a thread with C1 support but their conclusion is the fault is with windows.0 -
I am confused. Is the problem with windows or Capture one? [quote="Photocor" wrote:
I have also a thread with C1 support but their conclusion is the fault is with windows.
0 -
[quote="Steve Mac" wrote:
I am confused. Is the problem with windows or Capture one?[quote="Photocor" wrote:
I have also a thread with C1 support but their conclusion is the fault is with windows.
On my point of view its is a capture one issue.
The Phase One point of view is that it is a windows problem.
It was the reason why I wrote "I think you will make a lot of progress if you listen the users, even if you don't find immediatly the solution. It is better to say, "sorry, today we don't understand why, but we study your cases." than "it is your Windows installation"."
And now with a lot of tread viewed on different places, I am sure that it is a C1 problem.0 -
For me, with the new version (7.1.4) no crash when I "play" with the performance capture one!!
A very good thing.
Regards0 -
[quote="Photocor" wrote:
For me, with the new version (7.1.4) no crash when I "play" with the performance capture one!!
A very good thing.
We have had several crashes daily, since loading C17. Several support cases, blaming Nikon, the tether, the Mac and underpowered USB ports. I've felt this has been an issue with C17 since day one but no one would admit it. We loaded 7.1.4 on our macs yesterday and have been shooting on 2 computers with no crashes! Early days but a huge difference. It would be nice if C1 would be honest and stop wasting our time with crash logs and support cases. User forums like this are an invaluable source of information! I hope the stability continues for you (and me 😊 ).
Good luck.0 -
[quote="Steve Mac" wrote:
[quote="Photocor" wrote:
For me, with the new version (7.1.4) no crash when I "play" with the performance capture one!!
A very good thing.
We have had several crashes daily, since loading C17. Several support cases, blaming Nikon, the tether, the Mac and underpowered USB ports. I've felt this has been an issue with C17 since day one but no one would admit it. We loaded 7.1.4 on our macs yesterday and have been shooting on 2 computers with no crashes! Early days but a huge difference. It would be nice if C1 would be honest and stop wasting our time with crash logs and support cases. User forums like this are an invaluable source of information! I hope the stability continues for you (and me 😊 ).
Good luck.
I must strongly disagree that sending crash logs and submitting support cases are a waste of time. They are very valuable to us, and has helped us improve the overall quality of Capture One and will continue to do so.
I am however glad that you think the stability has improved.0 -
updated to 7.1.4 and crashes all the time..in fact it wont even run..just goes to a crash dump..have submitted my error logs
rolled back to 7.1.3 which was stable on my machine ,
deleted a system file as I was advised in another thread..still no good !!...must annoying product0 -
Tommo: I had a very similar crash-phenomenon here, the Support helped: just try to deactivate OpenCL by this (offcial) script: http://www.phaseone.com/en/~/media/Supp ... pencl.ashx
My graphic card don't support OpenCL, so it's not a big loss for me, but since I ran the script, 7.1.4 works, seems also to be more responsive e.g. for Adjustment Layer operations.
Regards,
Andras0 -
Hi Andras
My GC works fine with 7.1.3 with open CL enabled..in fact its a new card I bought purely to increase the productivity of of C1..( AMD 7870) .so updating to 7.1.4 and disabling open cl seems like a backwards step to me as it would increase load on the CPU as the GPU isn't being used as it should ?
what I cant make out is why one version will work and a supposed update to fix bugs etc is worse ...its quite annoying to say the least that high end software like c1 should be like this !0 -
[quote="Tommo1965" wrote:
Hi Andras
My GC works fine with 7.1.3 with open CL enabled..in fact its a new card I bought purely to increase the productivity of of C1..( AMD 7870) .so updating to 7.1.4 and disabling open cl seems like a backwards step to me as it would increase load on the CPU as the GPU isn't being used as it should ?
what I cant make out is why one version will work and a supposed update to fix bugs etc is worse ...its quite annoying to say the least that high end software like c1 should be like this !
You should not disable OpenCL unless you experience problems with the acceleration.0 -
im only getting problems with the latest update..version 7.1.4 0 -
[quote="Tommo1965" wrote:
im only getting problems with the latest update..version 7.1.4
It would help a bit if you could state what kind of issues?0 -
[quote="Christian Gr" wrote:
I must strongly disagree that sending crash logs and submitting support cases are a waste of time. They are very valuable to us, and has helped us improve the overall quality of Capture One and will continue to do so.
I am however glad that you think the stability has improved.
I have spent many hours dealing with this buggy software that now finally seems to be functioning with minimal crashes. We have changed nothing in our hardware, setup or workflow. So, after months of multiple daily crashes, beach balls and the program becoming unresponsive, we loaded 7.1.4 last Thursday and have only experienced one crash! When a major software update is released I assume you have tested the software on various system configurations. While I understand new software comes with new problems, this has been excessive. My point was it seems most of the research on this update was done after the release via crash logs and customer feedback.0 -
[quote="Steve Mac" wrote:
[quote="Christian Gr" wrote:
I must strongly disagree that sending crash logs and submitting support cases are a waste of time. They are very valuable to us, and has helped us improve the overall quality of Capture One and will continue to do so.
I am however glad that you think the stability has improved.
I have spent many hours dealing with this buggy software that now finally seems to functioning with minimal crashes. We have changed nothing in our hardware, setup or workflow. So, after months of multiple daily crashes, beach balls and the program becoming unresponsive, we loaded 7.1.4 last Thursday and have only experienced one crash! When a major software is update is released I assume you have tested the software on various system configurations. While I understand new software comes with new problems, this has been excessive. My point was it seems most of the research on this update was done after the release via crash logs and customer feedback.
We test each release on a lot of platforms and in many different ways, but we can never test all configurations. We always try to match our test-platforms to something we know the customers are using.
We have made a lot of changes to the code over the last few months, so I am glad that you have fewer problems now. I also hope that you will continue sending crash-reports and give feedback to us 😉0 -
I'm on 7.1.4, on Windows 7 Ultimate. 2 Xeon 5430's and 12 GB of RAM. This build is crashing a LOT. I can't seem to import files into the catalog, even when I keep them in "current location." It crashes when I exit. You have probably gotten about a half-dozen crash reports (from the crash reporter) in the last two days. 7.1.3 was working OK for me. 7.1.4 is definitely not. 0 -
What graphics adapter do you have ? Be sure to keep the drivers up to date 0 -
I rolled back to 7.1.3, and the crashes have stopped. C1 DOES get unbearably slow after a while, and has to be closed and restarted every few hours. I still believe the application has a memory leak someplace. 0
投稿コメントは受け付けていません。
コメント
24件のコメント