not sure what went wrong but there seems te be an big error in the image.module

Fatal error: Allowed memory size of 20971520 bytes exhausted (tried to allocate 1800 bytes) in ../public_html/new/includes/image.gd.inc on line 95

Fatal error: Allowed memory size of 20971520 bytes exhausted (tried to allocate 73 bytes) in ../public_html/new/includes/database.inc on line 102

Comments

drewish’s picture

drewish commented
Status: Active » Fixed

you need to increase php's memory limit, edit the php.ini. or move to the imagemagick toolkit... if you search through the closed issues you'll find this is a duplicate of a ton of issues.

jorisx’s picture

jorisx commented

hmm ok
I've added this to the settings.php 

ini_set('post_max_size', 			'10M');
ini_set('upload_max_filesize', 		'10M');
ini_set('memory_limit', 			'24M');

which helped :)

do you know when a final release for 6 will be ready ?
(i'm working on a production site with drupal 6 and I love it!)

Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.

smitty’s picture

smitty commented
Version: 6.x-1.x-dev » 5.x-1.9
Category: bug » feature
Status: Closed (fixed) » Active

I think this is a very stupid error. And you can't avoid it if you only have a limited memory on the server, ImageMagick isn't available and a user is going to upload huge images.
So: Isn't it possible to compare the needed memory for the processing of the image with the available server-memory and give the user a Drupal-error-message before the server displays a fatal error?

Hetta’s picture

Hetta commented
Version: 5.x-1.9 » 6.x-1.x-dev
Status: Active » Fixed

Feature requests go to 6.x-whatever first.
Please don't reopen closed issues; instead, make a new issue, preferably with a patch towards your suggestion.

Thanks.

Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.