DSLRUsers.com

Hi, I've downloaded Nikon Capture 4.2 and decided to put it's batch processing through it's paces. Something I've noticed quick smart is that this application hasn't been stress tested much at all. After processing about 200 NEFs it starts getting numerous failures mainly due to the fact that this application has a seriously memory leak when batch processing. My PC is installed with 1gb of paired 512mb Corsair XMS memory and has like 10gb free for virtual. Yet it runs out of virtual memory while batch processing. Seems like they do a lot of memory allocating but hardly any freeing of memory once it has processed an image. I really feel sorry for the people who purchased this program.

I run with 2Gb memory and allocated one full SATA 250Gb for virtual memory on another Hdd, I have no problems, Corsair XMS memory or other third party products are not difference in this type of works. I tried Corsair XMS before and did not see the difference, perhaps are good for overlocking and game PC.

Yeah, gaming is one of my other hobbies :0

Perhaps it works ok with 256gb of spare space but seriously you shouldn't need that amount of virtual because as it's processed one image it should free up the memory however it's not.

kipper wrote:Yeah, gaming is one of my other hobbies :0

Perhaps it works ok with 256gb of spare space but seriously you shouldn't need that amount of virtual because as it's processed one image it should free up the memory however it's not.

Hdd space and its prices are not an issue so why should we bother! Even with above in PSCS, they have the wing

Kipper,

I noticed this in NC 4.0 and 4.1 also. I have held off on calling this a memory leak in previous posts – it is not really. NC simply does not seem to free the memory properly. I find that after I have processed 20 or so images that I need to shut NC down to free memory properly. So far, I am having a good run with 4.2. Sure, this problem still exists, but the improvements in other areas make it worthwhile.

Cheers

Matt

I've noticed a similar problem, even without batch processing, the computer gets progressively slower with every photo I process.

phillipb wrote:I've noticed a similar problem, even without batch processing, the computer gets progressively slower with every photo I process.

Yes, it's and depend on how much memory do you have in your PC same as virtual

I have 512mb but I don't have that problem with Photoshop and I don't think the old version of NC was like that.

phillipb wrote:I have 512mb but I don't have that problem with Photoshop and I don't think the old version of NC was like that.

 PS behave difference with NC, 512mb is just for fun with NC

NC feature wise is good, but it's memory management is pos. Seriously memory management is 1st year compsci stuff and they shouldn't be releasing it with something this bad.

Guys I'd have to agree. NC sucks big time in memory management and like MattC says it's been there a while. I take the same action as already covered and do a quit & restart of NC when it starts to slow. I'm a programmer. If I wrote something that ate memory like this does and couldn't fix it I'd quit the profession. Freeing memory / garbage collection is a snack to program in any modern programming language.

Yep that's what I'm reduced to doing Stubbsy, limitting my process to say maybe 200 photos with 10gb of virtual memory free. Think it's eating about 2-4gb of virtual and won't free up until I close down NC. I have 3200 photos to process from my trip to JPEG, once I have them in JPEG I can quickly just go through and determine if they're keepers or put in the holding pile. What should of been a start and leave for a few hours process has been complicated by poor programming.

kipper

If all you want to do is convert from NEF to jpeg have a look at ThumbsPlus. It can read NEF and its what I use to batch convert NEF to jpeg. It's no NC replacement, more a Nikon View replacement, but It may solve your problem.