After updating to dev versions of views,date and media receive the following error when trying to bring up the media form to select media for a new page entry. No files were selected because the form was not loaded.
Fatal error: Out of memory (allocated 57671680) (tried to allocate 17152 bytes) in /modules/system/image.gd.inc on line 237

Views 7.x-3.1+83-dev
Date 7.x-2.1+11-dev
Media 7.x-2.0-unstable3+24-dev
Field entity 7.x-2.0-unstable3+16-dev

Comments

clearwaternazarene’s picture

clearwaternazarene commented

Update replaced Media 7.x-2.0-unstable3+24-dev
with Media 7.x-1.0-rc3+16-dev (hoping the more stable version would work)
Now the error displayed after clicking on select media button is "Error getting media." which was the original issue I was trying to solve when I upgraded from previous version of Media.

clearwaternazarene’s picture

clearwaternazarene commented

Update replaced Media 7.x-2.0-unstable3+24-dev
with Media 7.x-1.0-rc3+16-dev (hoping the more stable version would work)
Now the error displayed after clicking on select media button is "Error getting media." which was the original issue I was trying to solve when I upgraded from previous version of Media.

Also if I go to media/browser/list get the following error
Fatal error: Out of memory (allocated 57933824) (tried to allocate 4288 bytes) in modules/system/image.gd.inc on line 237

Fanaile’s picture

Fanaile commented

"Fatal error: Out of memory (allocated 57933824) (tried to allocate 4288 bytes) in modules/system/image.gd.inc on line 237"

This means that your site is reaching its limit for running PHP scripts. If you have a php.ini file, look for the resources for memory_limit and try raising that. It should look something like this (replace the numbers with what you need):


;;;;;;;;;;;;;;;;;;;
; Resource Limits ;
;;;;;;;;;;;;;;;;;;;

max_execution_time = 300     ; Maximum execution time of each script, in seconds
max_input_time = 500	; Maximum amount of time each script may spend parsing request data
memory_limit = 128M      ; Maximum amount of memory a script may consume (128MB)

If you don't have a php.ini file, you can create one and upload it to the root directory of your Drupal installation. Depending on who your host is, you may want to check and see if they have their own limitations placed; I have had issues in the past where I was trying to raise a site's memory_limit to 96MB and the host that the client was using wouldn't allow it higher than 64MB regardless of what the php.ini file said.

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented
Title: Fatal error: Out of memory (allocated 57671680) (tried to allocate 17152 bytes) in /modules/system/image.gd.inc on line 237 » PHP Fatal error: Out of memory in /modules/system/image.gd.inc

This is odd. We'll need some help from users experiencing this error helping to debug where this memory issues is coming from.

clearwaternazarene’s picture

clearwaternazarene commented

Reverted Media back to 7.x-1.0-rc2 - error message from previous version now back as "Error getting media."
At this point short of removing Media and starting over I will wait to see if Media team has any ideas.

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented
Status: Active » Closed (duplicate)

Thanks to thsutton he's helped figure out the cause of this bug and we're actively working on this for both 7.x-1.x and 7.x-2.x.
#1447790: image_load makes admin/content/media unusably slow

sdk’s picture

sdk commented

I am running a drupal multisite environment and all of the D7 installations running Media are affected by this bug. At first I thought it must have to do with a particularly content rich site where the error occurred first, but since the error appears on also newly created sites this mustn't be the reason.

Some observations about the creeping in:

At first everything went smooth but when files started accumulating, whenever I uploaded a file via the content field form, the described error message appeared. Strangely the file was still uploaded and showing up in the media browser but I couldn't access it via the content field browser.

I still could access the Media section in Contents though and choose from previously uploaded material. All of a sudden then not even the Media tab in the Content section was available anymore with the above error msg.

I just want to point out that there seems to be some "gradual" decay. Hope that helps and that you clever ppl find a way to fix this!

Best regards and lots of respect for the efforts.

sdk