Advanced search  

News:

cpg1.5.48 Security release - upgrade mandatory!
The Coppermine development team is releasing a security update for Coppermine in order to counter a recently discovered vulnerability. It is important that all users who run version cpg1.5.46 or older update to this latest version as soon as possible.
[more]

Pages: [1]   Go Down

Author Topic: memory allocation problem with EXIF display  (Read 7860 times)

0 Members and 1 Guest are viewing this topic.

mathfeel

  • Coppermine newbie
  • Offline Offline
  • Posts: 9
memory allocation problem with EXIF display
« on: January 16, 2008, 10:25:47 am »

If I turn ON reading of EXIF tag, some of the picture would give this error:
Code: [Select]
Fatal error: Allowed memory size of 33,554,432 bytes exhausted (tried to allocate 330,825,729 bytes) in /home/zpzstudi/public_html/coppermine/include/makers/canon.php on line 603
Why would canon.php tries to allocate this large (300MB?) amount of memory??
Logged

Joachim Müller

  • Dev Team member
  • Coppermine addict
  • ****
  • Offline Offline
  • Gender: Male
  • Posts: 47843
  • aka "GauGau"
    • gaugau.de
Re: memory allocation problem with EXIF display
« Reply #1 on: January 16, 2008, 10:53:45 am »

Review the file with an Exif viewer application to find out (e.g. Exifer or similar). The additional exif information might be just the straw that breaks the camel's neck - review the sticky on the upload board to find out about resources consumption that can lead to an error message as the one you experienced.
Logged

mathfeel

  • Coppermine newbie
  • Offline Offline
  • Posts: 9
Re: memory allocation problem with EXIF display
« Reply #2 on: January 16, 2008, 11:13:13 am »

Thanks, but what kind of extra EXIF information am I looking for?
Logged

Joachim Müller

  • Dev Team member
  • Coppermine addict
  • ****
  • Offline Offline
  • Gender: Male
  • Posts: 47843
  • aka "GauGau"
    • gaugau.de
Re: memory allocation problem with EXIF display
« Reply #3 on: January 17, 2008, 08:36:18 am »

I have no idea.
Logged

DJMaze

  • VIP
  • Coppermine addict
  • ***
  • Offline Offline
  • Posts: 831
    • Dragonfly CMS
Re: memory allocation problem with EXIF display
« Reply #4 on: February 24, 2008, 09:31:19 pm »

Currently I'm researching Jpeg Metadata for a complete new metadata reader.
Because Exifer (and the other PHP lib PHP JPEG Metadata Toolkit) are old and unmaintained.

Due to that i discovered that Exifer, and even PHP Exif extension, have serious issues with array data.

Your Canon is probably a newer model (EOS/1D maybe?) which has several MakerNote fields that contain a large array with integers.
For example the ColorBalance1 tag contains 692 integers in a EOS 40D MkaerNote.
In total the EOS 40D contains 16 arrays from 3 up till 692 entries inside an array!

So probably Exifer crashes on that.

I have no idea how to fix it since i prefer to work on the new library, but maybe this info helps you to find a solution.
Logged
There are 2 kinds of users in this world: satisfied and complainers.
Why do we never hear something from the satisfied users?
http://coppermine-gallery.net/forum/index.php?topic=24315.0

jabetcha

  • Coppermine newbie
  • Offline Offline
  • Gender: Male
  • Posts: 6
    • http://www.justfour.us
Re: memory allocation problem with EXIF display
« Reply #5 on: May 12, 2008, 10:57:58 pm »

If anyone else is experiencing this problem, the solution I have found is to download the latest exifer library (now at version 1.7) from here:
http://www.zenphoto.org/trac/wiki/ExifixerLibrary

Make backups of include/exif.php and include/makers/*.php

Copy the new the exif.php to <copperminedir>/include
Copy the files from the makers/*.php  to <copperminedir>/include/makers
Logged

Joachim Müller

  • Dev Team member
  • Coppermine addict
  • ****
  • Offline Offline
  • Gender: Male
  • Posts: 47843
  • aka "GauGau"
    • gaugau.de
Re: memory allocation problem with EXIF display
« Reply #6 on: May 13, 2008, 08:28:48 am »

Thanks for posting this piece of information. Apparently, zenphoto is continuing Jake Olefsky's exif library, so it's definitely a good place to look into. We (coppermine devs) need to look into this as well.
Logged

jabetcha

  • Coppermine newbie
  • Offline Offline
  • Gender: Male
  • Posts: 6
    • http://www.justfour.us
Re: memory allocation problem with EXIF display
« Reply #7 on: May 13, 2008, 07:48:11 pm »

Glad to be of assitance!
Logged

jabetcha

  • Coppermine newbie
  • Offline Offline
  • Gender: Male
  • Posts: 6
    • http://www.justfour.us
Re: memory allocation problem with EXIF display
« Reply #8 on: August 18, 2008, 08:06:15 pm »

I just checked the 1.4.19 release, and the latest version of this library is not included (still at v1.5). Do any of the devs know when you plan to update this library?
Logged

Joachim Müller

  • Dev Team member
  • Coppermine addict
  • ****
  • Offline Offline
  • Gender: Male
  • Posts: 47843
  • aka "GauGau"
    • gaugau.de
Re: memory allocation problem with EXIF display
« Reply #9 on: August 23, 2008, 08:03:37 am »

So far, nobody has volunteered to look into this. I have taken a note on the dev-only section of the board so this won't be forgotten. Probably won't go into any maintenance release of the cpg1.4.x series, but only (if at all) into cpg1.5.x.
Logged

jabetcha

  • Coppermine newbie
  • Offline Offline
  • Gender: Male
  • Posts: 6
    • http://www.justfour.us
Re: memory allocation problem with EXIF display
« Reply #10 on: December 21, 2008, 08:11:59 pm »

So far, nobody has volunteered to look into this. I have taken a note on the dev-only section of the board so this won't be forgotten. Probably won't go into any maintenance release of the cpg1.4.x series, but only (if at all) into cpg1.5.x.

Joachim,

I see from the main page that you are feature freezing 1.5x, but browsing the SVN repository, it still appears as if the old Exifer library is still being used. This causes Coppermine to FAIL when viewing thumbnails, normal size photos and full size when viewing any photos from a recent (3 years old or newer) Canon digital camera, if exif information is displayed. I consider this to be a serious BUG in coppermine that has not been addressed in several years.

I've replaced all the files, one-for-one, in the /include/makers directory with the latest exifer library, and my coppermine install has been working perfectly for over 2 years (except for when I upgrade and my files are overwritten!)

I would consider myself to be an extremely loyal coppermine user, and have been using it since pre-1.0 days, and submitted bugs and solutions to Grégory Demar, the creator of Coppermine.



Logged
Pages: [1]   Go Up
 

Page created in 0.024 seconds with 19 queries.