Skip to main content

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

A couple of minor issues with 6.0.1

Luke Miller
While I am generally able to accomplish everything version 6.0.1 is advertised to do I have a couple of exceptions. After I edit a folder of images I like to use the slideshow feature to play my edits so I can review them for consistency. My installation of 6.0.1 will not play more than about 10 images before it crashes. Interestingly this is true even when I am trying to play the downsized jpeg versions I processed.

Also batch rename will cause a crash as well. It will rename about a dozen images then crash. After recovering from the crash if I try to continue the batch rename starting with the image it crashed on - it will crash immediately without any further renaming. Obviously there are workarounds for these issues so they are not show stoppers.

I am very pleased with the rest of the functions that do work properly. My Windows XP machine has 3 GB of memory and when 6.0.1 crashes it is generally using more than 2 GB of it so I suspect a memory leak. Is anyone else experiencing this?
0

Comments

10 comments

Date Votes
  • Permanently deleted user
    There is a confirmed bug with virtual memory (at least for the WinXP 32-bit Express version) that consistently causes this crash in slideshows and some other functions (like dust spot and other large uses of memory) I was told to "please refrain from using the slideshow tool or extranious tools to a large degree, such as the clone tool to prevent the crash."

    I went thru a lengthy support case for this with the confirmation of the bug on Dec. 17th. I was told it is expected to be fixed in the next release. I am am very eagerly waiting as I have an activated v6, but still use v5 as 'refraining from using extraneous tools' is near impossible and the crashes are too annoying and frequent.

    (fyi - my system has 4GB of memory and a slideshow plays for 14 images, then on moving to the 15th it crashes, every time)
    0
  • Luke Miller
    Thanks Alex1

    I was hoping this was a known problem and that Phase One was working on it.
    0
  • Permanently deleted user
    I was told it could be up to 60 days until the next release where it may be fixed. I found that the more I let it crash the worse the crashes got, first just the app quitting, but then the system and eventually bluescreens and I needed to reinstall some drivers to get it back to normal. I re-installed everything and tried again, same pattern, mild recoverable crashes, then eventually bluescreens. So I don't use 6.0.1.
    0
  • Luke Miller
    [quote="Alex1" wrote:
    I was told it could be up to 60 days until the next release where it may be fixed. I found that the more I let it crash the worse the crashes got, first just the app quitting, but then the system and eventually bluescreens and I needed to reinstall some drivers to get it back to normal. I re-installed everything and tried again, same pattern, mild recoverable crashes, then eventually bluescreens. So I don't use 6.0.1.


    I haven't experienced the system crashes (yet), but your experience makes it sound like the memory leak in 6.0.1
    is allowing C1 data to overwrite operating system files much like a virus does. That is a serious problem. I think I will follow your example and go back to version 5 until this is resolved.
    0
  • Paul Steunebrink
    [quote="Luke_Miller" wrote:
    I haven't experienced the system crashes (yet), but your experience makes it sound like the memory leak in 6.0.1 is allowing C1 data to overwrite operating system files much like a virus does.

    A good general practice to preserve operating system integrity is to login and work with an account that has user-level (in contrast to administrator-level) privileges. You can set this in Control Panel, Users. It is also the best treat against any form of malicious code like viruses, worms, trojans and keyloggers.
    0
  • Permanently deleted user
    ^^ except of course that in diagnosing the problem PO support had me setup user accounts that had admin privileges. (not to mention uninstalling and reinstalling a lot of other stuff, etc.). A totally painful experinece I spend hours on just to find that the problem was not on my end, leaving me to clean up the mess. Even so, my system does not run the same as it did before I first installed v6 and started to get crashes.
    0
  • Luke Miller
    [quote="Paul_E" wrote:
    A good general practice to preserve operating system integrity is to login and work with an account that has user-level (in contrast to administrator-level) privileges. You can set this in Control Panel, Users. It is also the best treat against any form of malicious code like viruses, worms, trojans and keyloggers.


    Good point, I will do that. Thanks Paul.
    0
  • Permanently deleted user
    FYI i just installed v6.1 and did a quick slideshow test and it did not crash! Later today when I have more time I will use more CO functions to further test. But very early indications are that this is fixed - or at minimum improved.
    0
  • Luke Miller
    Thanks, Alex1
    I have been trying to download 6.1, but apparently the server is overloaded as the download data rates are very low. I'll try later.
    0
  • Luke Miller
    Finally got 6.1 downloaded and installed. The release notes are available on the US mirror site, but not the application, so it appears the entire world is trying to download it from the main site. So far 6.1 seems to resolve all the problems I was having with 6.0.1. So I am a happy camper. 😄
    0

Post is closed for comments.