Exif import problem in /modules/exif/lib/exifer/makers/olympus.inc

vola

Joined: 2006-10-02
Posts: 28
Posted: Wed, 2006-12-06 14:01

I'm importing my old 1.5 photos into the brand new 2.1.2, but I give an error from importer:

Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 55705601 bytes) in /web/htdocs/mysite/home/gallery2/modules/exif/lib/exifer/makers/olympus.inc on line 155

The problem is on 2 albums that contain photos made with an olimpus camera...

I search in google for a solution but i found only this:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=+358037

but there is no solutions about the problem.

A photo that causes the problem here

http://www.critrentino.it/gallery/view_photo.php?full=1&set_albumName=album193&id=P1010007

but the problem stills also on the other photo of this album...

The php runs with 32 megs of memory (enough for gallery i hope) and I cannot change it.

Seems a problem with exif parsing, any ideas?


G2 version: 2.1.2
G1 version: 1.5

PHP memory limit: 32M
--

 
valiant

Joined: 2003-01-04
Posts: 32509
Posted: Wed, 2006-12-06 17:21

tried your example image with the current nightly snapshot of g2.2.
couldn't reproduce the problem. the memory usage didn't go beyond normal levels, certainly not beyond 30 MB or so.

there have been some changes since g2.1.2 in our copy of the exif library and some of them should help to prevent memory usage issues.

 
vola

Joined: 2006-10-02
Posts: 28
Posted: Wed, 2006-12-06 17:57

Maybe the usage during import is more, due to import process... i can't test with the 2.2 for now...

so for finish up the imports i'd commented out the olimpus related things in the exif.inc file.

 
valiant

Joined: 2003-01-04
Posts: 32509
Posted: Wed, 2006-12-06 18:23

while importing, i'd disable the exif module anyway.
that's what we recommend in the migration instructions, i thought.

 
vola

Joined: 2006-10-02
Posts: 28
Posted: Wed, 2006-12-06 18:47

ok :)

But the strange thing was this happen only on olimpus photos.

Thanks!

 
cronky

Joined: 2008-04-10
Posts: 1
Posted: Thu, 2008-04-10 23:17

For those affected by this who can't upgrade (like me at the moment) I've managed to find a work-around - blog post here: http://blog.cronky.net/blog/?p=98

Hope its useful!