メインコンテンツへスキップ

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

CO6 Crashing constantly in Vista

コメント

23件のコメント

  • Permanently deleted user
    Yes, it has happened to me before on my Vista x64 system.

    Watch the task manager Working Set and Peak Working Set numbers. When the Working Set is getting close the Peak Work Set (high water mark), CO 6 becomes sluggish and is prone to crash.

    You could try cleanmem, a little freeware utility, to clean up unused memory periodically. It does not solve the root cause but does prolong the life of the CO 6.

    I have a memory leak support case open for this issue.
    0
  • Vesa_Ekholm
    It crashes all too often with Win7 32bit too...

    Yesterday - I stopped counting after 5 crashes in one hour 😕
    0
  • HKGuns
    Thanks, glad to know it isn't just me......This release appears not to have been tested very well.

    It is so bad for me I would consider pulling this release if it were my company. I'll not open a case then and let them work on this one through your case.
    0
  • Permanently deleted user
    I too have frequent crashes winXP SP3 w/ATI Radeon 3800 card with an open service case with many things tried with no indication that this is any closer to resolution or understanding.
    0
  • NNN634236227273766629
    Win 7 64 bit, too. Just occasionally.
    0
  • Jim MSP
    I'm using Win 7 64; but no crashes yet.
    However, with Open CL running, I start to see some strange effects when processing photos the longer I use the program.
    They seem to be associated with changing contrast or using the clarity slider.
    I suspect it is due to memory leakage issues.
    I will try to run some tests later; but this could also relate to your crashes.

    BTW, I paid for my upgrade, and I hate to be a beta tester when I am paying for it.
    0
  • Triumph Steve
    My 32-bit Express version crashes when I am deleting many RAW images, shutting down and giving me a pop-up window where I can enter in my name and e-mail address and send a tech report to Phase One.
    0
  • Kees
    I am currently using C1 R4.8 and am now trying out C1R6 (because of DSLR upgrade from K100 to K7)

    I am still not sure if I should stick with the light edition (Express), or move on to Pro,
    as I like the extra features of the Pro version.

    When I start up the demo in Pro, CaptureProcess.exe imidiately crashes every time (also on administrator).
    After closing the error message, C1R6 seems to work correct: I can process images and so on. 😕

    I do not have this problem with the Express version, but I will sure try it out thoroughly before making a decision.

    WinVista 32 bit Home Premium SP1 on a AMD Athlon 64 X2 and 2 GB memory

    I have contacted support about this (CASE number 83831). I am a programmer myself - different kind of software - and I know how important it is that you get feedback from your customers.
    0
  • Paul Steunebrink
    [quote="Kees" wrote:
    ...
    When I start up the demo in Pro, CaptureProcess.exe imidiately crashes every time (also on administrator).
    After closing the error message, C1R6 seems to work correct: I can process images and so on. 😕

    I believe CaptureProcess.exe is a process involved in tethered shooting. This should explain that you can use the program normal after closing the error and that you only have this with Pro. Because you shoot Pentax, you are not after Pro for tethering. For the trial, I suggest you go into Preferences, Capture tab, where you can find a list of camera brands in Enabled Tethered Support. By default they are all selected. Deselect all. This does not stop the CaptureProcess.exe process from starting, but it is smaller. See what happens.

    And you might want to update your Vista. Vista SP2 is a requirement for CO 6 and could therefore the cause of your problem as well. And you are on 6.0.1, are you?
    0
  • Kees
    Paul, thank you for your reply. This is usefull information.

    The version I am testing is indeed 6.0.1 (build 44939).

    I have done one attempt to install SP2 but did't succeed.
    b.t.w. the manual says SP1 in the requirements

    I will go and try to switch off the tethered shooting options this evening, when I am back home.

    Kind regards,

    Kees
    0
  • Paul Steunebrink
    [quote="Kees" wrote:
    ...
    I have done one attempt to install SP2 but did't succeed.
    b.t.w. the manual says SP1 in the requirements

    Contradiction in system requirements is not uncommon at this part of the world. I did read Vista SP2 in both the release notes and online help, but apparently it says SP1 elsewhere.
    But the fact you had difficulties installing SP2 is more worrying however re. system health. This could have a common cause with the tethering issue, but that is nothing more than a wild guess on my behalf.
    0
  • Kees
    it is the pdf download of the manual that still says SP1.

    Just don't have a very fast and stable internet connection at home.

    I will give SP2 another try this evening. Have the complete SP2 downloaded in advance, ready for install.
    0
  • Kees
    For the trial, I suggest you go into Preferences, Capture tab, where you can find a list of camera brands in Enabled Tethered Support. By default they are all selected. Deselect all. This does not stop the CaptureProcess.exe process from starting, but it is smaller. See what happens.


    well, this did't help....

    And you might want to update your Vista. Vista SP2 is a requirement for CO 6 and could therefore the cause of your problem as well


    and this did't help either.

    The fault logs created by C1 seems to indicate troubles with accessing color profile files, but the files mentioned do exist.
    0
  • Paul Steunebrink
    [quote="Kees" wrote:
    ...
    The fault logs created by C1 seems to indicate troubles with accessing color profile files, but the files mentioned do exist.

    Problem with file access does not mean the file does not exist but that the program can not access it (for whatever reason). This sometimes occur when CO 6 has not selected a specific output profile but 'Embed Camera Profile' to the output file in the Process Recipe (Output tool tab). If that is the case, select another profile for testing like AdobeRGB or sRGB.
    0
  • Kees
    I have sRGB selected.

    anyway, here is a link to a copy of some logfiles:

    01 Normal start under Administrator account.zip
    0
  • Paul Steunebrink
    The warning about profiles in the Application.log is not something you should worry about. It is a warning only, and I noticed the same on my (assumed healthy) system (that does not necessarily comfort you 😉). Apart from the tethering (captureprocess.exe) issue, is there any issue you currently experience with your CO 6 trial?

    And CO 6 should run perfectly under a non-administrative user account, just for the record. Installation and activation requires an administrative account.
    0
  • Kees
    One thing I could try is uninstalling and reinstalling because my system runs on SP2 now.

    Normally I run everything under a non-admin account, and C1 seems to behave the same under admin and non-admin.

    The few files (shot inside at low light) I have processed so far look OK, did not have much time for serious shooting at daylight however. I guess I should take some old PEF's

    (It's dark when I leave home in the morning, and it's dark when I get home again in the evening)
    0
  • Paul Steunebrink
    [quote="Kees" wrote:
    ...
    (It's dark when I leave home in the morning, and it's dark when I get home again in the evening)

    I know, it's the dark ages again in the northern hemisphere. But light is coming back, I promise! 😉
    0
  • Kees
    Did some playing around with PEF's from the K100. Image colors look similar to me. I noticed very small differences in color temperature. Just a few degrees, nothing to worry.

    One issue: if I delete one image and select the next image, the image viewer stays grey, the screen is not updated until I rescale the image selector down below. 2x <CTRL>B (close, open the image selector) has the same effect.
    It does this in both Express and Pro, the behaviour is a little different. Sometimes I see the windows desktop in the right of the screen.

    If I delete more images at the same time there is no problem.

    Is this a known problem?
    0
  • Paul Steunebrink
    Not that I am aware off, maybe someone else here knows.
    0
  • Kees
    Did some tests this morning:

    first removed Capture One
    then reboot PC
    reinstall Capture One

    Under administrator account: deleting files does not result in a problem.

    Under my user account:
    If I delete a single file, the image disappears from the viewer.
    Sometimes, the next image shows up.

    But most of the time, the Viewer becomes completely black or grey with 'no image selected'.
    When doing a screen resize or just clicking on the upper edge of the image browsers titlebar, the viewer is refreshed and the selected image is shown.

    (So reinstalling under SP2 seems to solve the problem a little bit, the behaviour in Express and Pro is similar now)
    0
  • Kees
    The release of 6.1 solved the problem of crashing CaptureProcess at startup.
    0
  • Paul Steunebrink
    [quote="Kees" wrote:
    The release of 6.1 solved the problem of crashing CaptureProcess at startup.

    Good to hear. Thanks for the feedback.
    0

投稿コメントは受け付けていません。