← Back to team overview

phatch-dev team mailing list archive

[Bug 469701] Re: Crash\memory leak when renaming RAW (ARW) files

 

Hey there Stani, I'm also experiencing this bug. I have a core2quad with
4 Gb of memory (3.9 Gb available, with a PAE-enabled kernel). I wanted
to simply convert 432 Nikon (.NEF) files to jpeg after resizing.
Symptoms are the same as julez's, memory usage climbing (currently 1.3
Gb used while only 32 files have been processed!), and once in a while,
a file fails to convert, citing the cannot allocate memory error.

To some extent, I'm glad it's failing. I would have filled my 4 Gb of
RAM. Why doesn't Phatch free memory after each image?

** Changed in: phatch (Ubuntu)
       Status: Incomplete => Confirmed

-- 
Crash\memory leak when renaming RAW (ARW) files
https://bugs.launchpad.net/bugs/469701
You received this bug notification because you are a member of Phatch
Developers, which is subscribed to Phatch.

Status in Phatch = Photo & Batch!: Incomplete
Status in “phatch” package in Ubuntu: Confirmed

Bug description:
Binary package hint: phatch

I have a rename action which is working fine on JPGs.  When applied to RAW image files (Sony ARW format) the rename works ok for a few files but then crashes with the following error:

Error: Unable to open file: /xxxx/xxxxx/xxxxx/xxxx/xxxxx/DSC00786.ARW:
(12, 'Cannot allocate memory')

Monitoring the phatch process in top shows the memory utilisation increase as it works through a batch

Restarting the phatch with the same action on the same (remaining photos) and it continues with the image that caused an issue

Images not attached as multiple large files are required (can be sent on request)

Ubuntu 9.10
Phatch 0.2.4-1