CO crash solution ...
Everyone once in while ... maybe 30-40% of the time ... my CO 7.1.1 will issue a crash alert just after I've closed the app. My CO 7.1.1 doesn't at all crash when I'm using it, just shortly after closing it down. The prompt is the usual crash prompt: "CO has suddenly and unexpectedly quit" followed by all of the gibberish that only a tech genius could possibly read.
I'm running all of the time from external drives, including boot up and app access ... and we all know that CO doesn't enjoy running from an external source. Well, that's my set up, and I have no intention of changing it. LR and other apps work just fine this way.
Last week I decided to try closing down CO in a different way: I go to the folders menu and make sure that the drive CO is on is the drive that's selected before closing .... that is, if I'd been working in a sub-folder somewhere on of my external drives, or even from a flash disk, I change the folder to the main drive I use for boot-up and app access (the drive where CO is located, among others). This seems to have stopped the abrupt shut-down crashes ... at least, up to this point. I haven't had a single crash since closing down CO this way.
Give it a try. Let us know if it works for you as well.
- Steve
I'm running all of the time from external drives, including boot up and app access ... and we all know that CO doesn't enjoy running from an external source. Well, that's my set up, and I have no intention of changing it. LR and other apps work just fine this way.
Last week I decided to try closing down CO in a different way: I go to the folders menu and make sure that the drive CO is on is the drive that's selected before closing .... that is, if I'd been working in a sub-folder somewhere on of my external drives, or even from a flash disk, I change the folder to the main drive I use for boot-up and app access (the drive where CO is located, among others). This seems to have stopped the abrupt shut-down crashes ... at least, up to this point. I haven't had a single crash since closing down CO this way.
Give it a try. Let us know if it works for you as well.
- Steve
0
-
Update to 7.1.3 should do the trick for you. Let us know. 0 -
[quote="Paul_Steunebrink" wrote:
Update to 7.1.3 should do the trick for you. Let us know.
I already found a solution, as per my post. Did you not read the entire post?
- Steve0 -
[quote="SMG Photography" wrote:
[quote="Paul_Steunebrink" wrote:
Update to 7.1.3 should do the trick for you. Let us know.
I already found a solution, as per my post. Did you not read the entire post?
- Steve
Yes, I did, but the issue you descibed is solved in the update, so easier to install it.0 -
[quote="Paul_Steunebrink" wrote:
[quote="SMG Photography" wrote:
[quote="Paul_Steunebrink" wrote:
Update to 7.1.3 should do the trick for you. Let us know.
I already found a solution, as per my post. Did you not read the entire post?
- Steve
Yes, I did, but the issue you descibed is solved in the update, so easier to install it.
I've downloaded 7.1.3 and will run that for awhile.
- Steve0 -
If you run a dtrace as you are getting ready to quit, you will see see that C1 is scanning through your hard drive, and I believe building its cache of your folder structure that you use in the first tab. If you wait until it is done, it will not crash, quit before and it will. It even seems to looking for some non-existent test file that must have resided on the machine the app was built on.
7.1.3 does fix this either by allowing a more graceful quit, or how it handles going through your folder structures.
It may be that selecting your root drive minimizes what it scans, ie it only traverses x sub folders, so perhaps that is why it helped.
-Peter0 -
[quote="NNN634969704951552289" wrote:
If you run a dtrace as you are getting ready to quit, you will see see that C1 is scanning through your hard drive, and I believe building its cache of your folder structure that you use in the first tab. If you wait until it is done, it will not crash, quit before and it will. It even seems to looking for some non-existent test file that must have resided on the machine the app was built on. 7.1.3 does fix this either by allowing a more graceful quit, or how it handles going through your folder structures. It may be that selecting your root drive minimizes what it scans, ie it only traverses x sub folders, so perhaps that is why it helped.
-Peter
Very interesting and very helpful. 7.1.3 hasn't crashed once. 7.1.1. still crashes from time to time, but I'm hardly using it now and will probably dump it soon. 7.1.3 works without flaw so far.
- Steve0
Post is closed for comments.
Comments
6 comments