ACDSee Pro 2 and 2.5

Back to Topic OverviewPost New Reply

occasional crashes in RAW processing

(8 posts)

  • Marc Sabatella
    Moderator

    Reports of sporadic crashes in RAW processing have come up from time to time. I rarely saw this before, but with 2.5, I'm seeing it more often. Unfortunately, of course, nothing reproducible - if I restart ACDSee and revisit the same file, it's always OK.

    Posted On September 19, 2008 - 10:25 AM (1 year ago) (Permalink to this post)

  • kaledi
    Member

    Hi,
    I've just upgraded from 2.0 to 2.5 and where as previously Pro2 was rock solid, 2.5 seems to crash quite frequently when viewing RAW files. The scenario I've observed is that the crashes occur when I'm scrolling through raw files in the viewer and Pro2.5 is generating a high quality render for viewing.
    Of note, the RAW files in question are from a KonicaMinolta Dynax 5D
    Cheers

    Posted On September 20, 2008 - 03:24 AM (1 year ago) (Permalink to this post)

  • fonebone
    Member

    I also can confirm this. It seems to happen not only when batch processing RAW file but when doing batch processing in general (also with jpeg images).
    Can anybody confirm my observation I documented in this post, I could imagine that there is a relationship...

    Posted On September 20, 2008 - 09:29 AM (1 year ago) (Permalink to this post)

  • Marc Sabatella
    Moderator

    fonebone said:

    I also can confirm this. It seems to happen not only when batch processing RAW file but when doing batch processing in general (also with jpeg images).
    Can anybody confirm my observation I documented in this post, I could imagine that there is a relationship...

    I hadn't known about the thread option in task manager - thanks for the pointer!

    I can confirm that while I haven't done anything with ACDSee recently - it's been just sitting there all day - it had 25 threads open when I just checked. After closing it and restarting, it had 23. So it does seem 2 additional ones had been created and left running at some point in the last day or so it had been running. I have no idea how significant this is, but thanks again for pointing this out - gives me something to check out when I have problems.

    BTW, while I had several crashes late Thursday night processing a bunch of files, I had none yesterday processing those same files again and a bunch of new ones.

    When I did see a crash, it was usually more or less immediately upon entering RAW processing on a given image. Often the first thing I did was hit the Crop button - before it was even done displaying the preview and current settings - and before it could display the relevant tab, it crashed. But I don't know if it was hitting Crop that *caused* the crash, or if it would have crashed when it was done with the preview.

    Posted On September 20, 2008 - 01:30 PM (1 year ago) (Permalink to this post)

  • icewater
    Member

    Occasional crashes in RAW processing, your the lucky one...
    I was doing raw processing everyday with Pro 2.0 Just upgraded to 2.5 and I cant even open a Raw, it just crashes imediatly.

    Using two sonys R1 and A700 Raw and Craw and Windows Vista hp quad core Q6600 3 gig ram

    Kinda of funny, Ive never had a program crash in my life as much as Pro2.0, boy was I excited when I saw the upgrade, GREAT, they fixed some stufffff.
    After instulation, and reboot, I started the new program, and 3 seconds later... it crashed.. at that moment I knew, big new program, same ol crap.

    I see a New car here with fancy cup holders, and a sun roof, shiny wheels, but the engine still wont start.

    Waiting for tech support one more day, then going back to the old version.

    What else can I do?

    I guess they figured they can make more money by always selling new bata programs and never perfecting any of them.

    I have been Using the Editor 2008 as well, same story, crash every half hour like clock work.

    Perhaps Photoshop purchased Acdsee, and is just punishing us for not buying their program?

    Posted On September 21, 2008 - 01:19 AM (1 year ago) (Permalink to this post)

  • fonebone
    Member

    Marc Sabatella said:

    I hadn't known about the thread option in task manager - thanks for the pointer!

    I can confirm that while I haven't done anything with ACDSee recently - it's been just sitting there all day - it had 25 threads open when I just checked. After closing it and restarting, it had 23. So it does seem 2 additional ones had been created and left running at some point in the last day or so it had been running. I have no idea how significant this is, but thanks again for pointing this out - gives me something to check out when I have problems.

    BTW, while I had several crashes late Thursday night processing a bunch of files, I had none yesterday processing those same files again and a bunch of new ones.

    When I did see a crash, it was usually more or less immediately upon entering RAW processing on a given image. Often the first thing I did was hit the Crop button - before it was even done displaying the preview and current settings - and before it could display the relevant tab, it crashed. But I don't know if it was hitting Crop that *caused* the crash, or if it would have crashed when it was done with the preview.


    try the following:
    • select a few jpg images
    • start the Batch Processor
    • select the "Shadows/Highlights" operation
    • play a little bit with e.g. the color boost control (also works with the other ones)
    • watch the number of threads in task manager

    I think this is the most serious case I was able to find. The number of threads keeps increasing when you actually run the batch and the shadow/highlights operation is included (which is most often the case when I use batch processing)....
    <u>Note:</u> when I prepared this response and was playing around with ACDSee for the scenario, guess what, it crashed
    It could be that this is a general misbehavior of the shadows/highlights tool because I also observe the increasing number of threads when working with the tool on a single image (independent of whether it is JPEG or RAW)

    Posted On September 21, 2008 - 05:26 AM (1 year ago) (Permalink to this post)

  • Chippy
    Moderator

    Interesting thread.
    I just tried some of the above, and can confirm a lot that has been stated.
    But could not get it to crash.

    If I open ACDSee and do some editing, and then close it,in Task manager, it is still running, although the thread cont drops.
    Opening ACDSee again, I then have a 2nd instance of ACDSee showing. Do some editing, and close. ACDSee 2nd instance is still running.
    Open again, and do no editing, (Now I have three instances of ACDSee running),just browse from directory to directory, and then close , I am back to two instances running.

    I was going to try and see how many instances I could get, but time.....

    So, some of these crashes could be caused by haveing multiple instances of ACDSee running, and it is not releasing memory, etc, to the OS.(Vista Ultimate)

    Memory leak?

    Just checked again, and there is still 2 ACDSee processes running.Had to do a "End Process" on each.

    Posted On September 21, 2008 - 08:31 PM (1 year ago) (Permalink to this post)

  • RDFIII
    Member

    I have had the same problem with RAW files and there were no multiple instances of ACDSee running.

    Posted On September 23, 2008 - 06:10 AM (1 year ago) (Permalink to this post)

Subscribe to this topic via RSS

Reply

You must log in to post.