Crash\memory leak when renaming RAW (ARW) files

Bug #469701 reported by julez
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Phatch
Confirmed
Medium
Unassigned
phatch (Ubuntu)
Confirmed
Undecided
Unassigned

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

Revision history for this message
julez (4julez+launchpad) wrote :
Revision history for this message
Stani (stani) wrote :

Does the memory increase also happen with jpeg files? How much memory does your system have?

To debug I'll need the photo files as well. You can send them to me privately if you prefer.

Changed in phatch:
assignee: nobody → stani (stani)
status: New → Incomplete
Stani (stani)
Changed in phatch (Ubuntu):
assignee: nobody → stani (stani)
status: New → Incomplete
Revision history for this message
Jeff Fortin Tam (kiddo) wrote :

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
Revision history for this message
Jeff Fortin Tam (kiddo) wrote :

Further info:
- my RAM was far from full when this occured
- this is not specific to an image in particular. If I copy out the .NEF at which this occured, and try to run phatch on it, it works without problems.

Revision history for this message
Jeff Fortin Tam (kiddo) wrote :

Make 400 copies of this file and try to do batch resizing and exporting to jpeg on them.

Revision history for this message
Stani (stani) wrote :

Hi Matthieu,
Could you profile this? Phatch uses a subprocess with dcraw behind the scenes to open RAW images. Let me know if you are not interested.

Changed in phatch:
assignee: stani (stani) → Matthieu Amiguet (matthieu-amiguet)
importance: Undecided → Medium
milestone: none → 0.2.7
status: Incomplete → New
Changed in phatch (Ubuntu):
assignee: stani (stani) → Matthieu Amiguet (matthieu-amiguet)
Changed in phatch:
status: New → Confirmed
Revision history for this message
Stani (stani) wrote :

@Jean-François Fortin Tam

In order to find out if these bugs are related: can you reproduce this bug?
https://bugs.launchpad.net/phatch/+bug/525999

Revision history for this message
Stani (stani) wrote :

Matthieu, feel free to reassign this bug to you in case you want to fix it.

Changed in phatch:
assignee: Matthieu Amiguet (matthieu-amiguet) → nobody
Stani (stani)
Changed in phatch (Ubuntu):
assignee: Matthieu Amiguet (matthieu-amiguet) → nobody
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.