Hello Danny,

I've uninstalled the previous versions of PhotoDirector, so I'm not able to make any direct comparisons at the moment.

Though I'm no expert on matters technical, such as coding to fix memory leaks, I have just replicated your circumstance importing 80 CR2 files from a couple of different cameras (5DMkIII & & 40D).

On my fairly modest set-up, PhD4 imported & rendered the RAW files quite smartly (under 30 seconds). It did take some time to generate the thumbnails & there was a short "thinking" period after import, but it didn't appear to me that there was a particular issue with the software.

I had done this previously with PhD3 & didn't notice any issues then either.

The difference may be that I started with a new project then imported, rather than opening a project built in PhD3.

PIX PIX YouTube channel

Thanks Pix, I've had no trouble with new projects so far, only with this converted project...

Danny danny

Danny,

That's a comfort! So you think the issue is only evident in projects built in previous versions of PhD?

Just to test & confirm, I'll re-install PhD3 & replicate your steps. If there's something in this, I'm sure the R&D people would want to be aware.

I'll let you know how I go. Thank you for reporting back.

PIX PIX YouTube channel

Hello Pix,

I can confirm that it only happens while PD4 is building and displaying the thumbnails for the converted project for the first time. You see the memory use of PD4 grow to over 2 GB with full CPU and at that moment it stops displaying new thumbnails and after some time says that "not enough memory is available".

No issue at all while importing new pics in the same converted project.

Once PD4 has been restarted enough times to generate all the thumbnails the problem is gone.

Danny danny

Quote: Once PD4 has been restarted enough times to generate all the thumbnails the problem is gone.

I discovered that it's not really a memory leak but a problem in the way the thumbnail generation is implemented.

If I scroll through the thumbnails faster than PD4 can generate them, it tries to generate so many at once that it runs out of memory.

But if I wait until all visible thumbnails are generated and displayed (when the busy cursor disappears), PD4 releases all the memory again and I can scroll to the next page, wait until those are generated (memory again going up to the max 32 bit limit), and so on...

So the fix would be to limit the number of thumbnails that PD4 tries to generate at the same time (by not trying to keep up with the scrolling), I think this would actually speed up the process....
danny

Hello Danny,

I'm glad you're closer to a resolution. I've tested multiple times:
- importing up to 140 RAW images (CR2) in one hit
- opening projects built in PhD3 containing large numbers of the same files

There have been times I've caused my (fairly modest) system to slow down. It does take time for thumbnails to generate after import but I don't find it interferes with my workflow. After all, in my testing, I was asking PhD to import & generate thumbs for 100+ RAW images (each about 30MB).

Memory usage, observed in Task Manager, is high at these times but I would expect that. In my testing, I found no difference between how PhD3 & PhD4 handled the open/import process.

PIX PIX YouTube channel

Hi Pix,

This only happens when scrolling through the thumbnails of a large PD3 project that has just been upgraded to PD4, the thumbnails are apparently regenerated "on demand" by PD4 when you scroll through them for the first time.

No such problems when importing new images into a PD4 project (upgraded project or not).

Danny danny

I am having an out of memory issue as well. Admittedly my system is a bit anemic (3gb RAM on WinXPsp3) so this may be the root of my issues. I am finding when I am browsing thumbnails as the OP described I will start to get out of memory errors. The images in my library are a mix of jpg and NEF raw, amounting to about 10mb for unprocessed images. The software seems to work for a bit, then wants to crash as it runs out of memory - I can watch this happening in task manager as PhD consumes over a gb of available memory. I am only running a trial version at the moment, so far i am really liking this software but if this is going to be an issue its obviously a deal killer for me.

I currently have Photodirector 3, and was actually considering upgrading. On PD3, I actually get out of memory errors at times with just a handful of jpgs. Literally with ten jpg images from a Canon T3, and memory error. Not on all images either, just when I try to select certain ones.

I'm running Windows 8, with 4GB ram. Plenty of room for swap files. When this does occur, the system still shows about 35% of ram still available???

I was really hoping this would be corrected on PD4. Seems not to be the case?