imagefield causing excessive cache_set queries, database entries and memory use

typo fix

Hi @quickstretch, APC is not currently enabled on this website; is there another way that the memory could be taxed? As mentioned my sites has all modules turned off except Ubercart, Imagefield and CCK and the problem still ocures.

The idea of putting some breaks in the cache_set is a good direction to go, hopefully the code will reveal its secrets to me soon.

Thanks again.

So when I look at xhprof all I see is that cache_set is being called once, but the serialized data it puts into it is 100+MB. When I turn off ImageField is goes back down to much more "normal" levels.

When I look into the serialized data, it has a gigantic amount of data in it right after the "default image" text, even though I have no default image selected. I get this huge amount of data even when I go to the node/add form.

It goes from a 10kb cache_form entry to one of 7mb before any images are added.

If it is useful, here is a chunk of the serialized data, right before it goes into unended binary data:

";s:18:"allowed_values_php";s:0:"";s:6:"widget";a:7:{s:13:"default_value";a:1:{i:0;a:1:{s:5:"value";s:1:"0";}}s:17:"default_value_php";N;s:5:"label";s:10:"Sort Order";s:6:"weight";s:1:"1";s:11:"description";s:0:"";s:4:"type";s:20:"optionwidgets_select";s:6:"module";s:13:"optionwidgets";}}s:17:"field_image_cache";a:16:{s:10:"field_name";s:17:"field_image_cache";s:9:"type_name";s:17:"lighting_products";s:16:"display_settings";a:6:{s:6:"weight";s:1:"2";s:6:"parent";s:0:"";s:5:"label";a:1:{s:6:"format";s:6:"hidden";}s:6:"teaser";a:2:{s:6:"format";s:6:"hidden";s:7:"exclude";i:0;}s:4:"full";a:2:{s:6:"format";s:6:"hidden";s:7:"exclude";i:0;}i:4;a:1:{s:6:"format";s:6:"hidden";}}s:13:"widget_active";s:1:"1";s:4:"type";s:9:"filefield";s:8:"required";s:1:"0";s:8:"multiple";s:1:"1";s:10:"db_storage";s:1:"0";s:6:"module";s:9:"filefield";s:6:"active";s:1:"1";s:6:"locked";s:1:"0";s:7:"columns";a:3:{s:3:"fid";a:3:{s:4:"type";s:3:"int";s:8:"not null";b:0;s:5:"views";b:1;}s:4:"list";a:4:{s:4:"type";s:3:"int";s:4:"size";s:4:"tiny";s:8:"not null";b:0;s:5:"views";b:1;}s:4:"data";a:3:{s:4:"type";s:4:"text";s:9:"serialize";b:1;s:5:"views";b:1;}}s:10:"list_field";s:1:"0";s:12:"list_default";i:1;s:17:"description_field";s:1:"0";s:6:"widget";a:262163:{s:15:"file_extensions";s:11:"gif jpg png";s:9:"file_path";s:0:"";s:18:"progress_indicator";s:3:"bar";s:21:
"max_filesize_per_file";s:3:"512";s:21:"max_filesize_per_node";s:4:"2560";s:14:"max_resolution";s:1:"0";s:14:
"min_resolution";s:1:"0";s:3:"alt";s:0:"";s:10:"custom_alt";i:1;s:5:"title";s:0:"";s:12:"custom_title";i:1;s:10:"title_type";s:9:"textfield";s:13:
"default_image";N;s:17:"use_default_image";i:0;i:0;b:0;i:1;b:0;i:2;b:0;i:3;b:0;i:4;b:0;i:5;b:0;i:6;b:0;i:7;b:0;i:8;b:0;i:9;b:0;i:10;b:0;i:11;b:0;i:12;b
:0;i:13;b:0;i:14;b:0;i:15;b:0;i:16;b:0;i:17;b:0;i:18;b:0;i:19;b:0;i:20;b:0;i:21;b:0;i:22;b:0;i:23;b:0;i:24;b:0;i:25;b:0;i
:26;b:0;i:27;b:0;i:28;b:0;i:29;b:0;i:30;b:0;i:31;b:0;i:32;b:0;i:33;b:0;i:34;b:0;i:35;b:0;i:36;b:0;i:37;b:0;i:38;b:0;i:39
;b:0;i:40;b:0;i:41;b:0;i:42;b:0;i:43;b:0;i:44;b:0;i:45;b:0;i:46;b:0;i:47;b:0;i:48;b:0;i:49;b:0;i:50;b:0;i:51;b:0;i:52;b:
0;i:53;b:0;i:54;b:0;i:55;b:0;i:56;b:0;i:57;b:0;i:58;b:0;i:59;b:0;i:60;b:0;i:61;b:0;i:62;b:0;i:63;b:0;i:64;b:0;i:65;b:0;i:
66;b:0;i:67;b:0;i:68;b:0;i:69;b:0;i:70;b:0;i:71;b:0;i:72;b:0;i:73;b:0;i:74;b:0;i:75;b:0;i:76;b:0;i:77;b:0;i:78;b:0;i:79;
b:0;i:80;b:0;i:81;b:0;i:82;b:0;i:83;b:0;i:84;b:0;i:85;b:0;i:86;b:0;i:87;b:0;i:88;b:0;i:89;b:0;i:90;b:0;i:91;b:0;i:92;b:0
;i:93;b:0;i:94;b:0;i:95;b:0;i:96;b:0;i:97;b:0;i:9

(and many more lines of binary data {6MBs worth...})

I rolled back to imagefield and filefield 3.2 just to see if the extra large serial data would go away, but it is still present. Can anyone decode the above to see if it is "normal", is it loading a default image somewhere weird? I did set just now my imagefield to only accept files of less than 512kb but it still cahces these very large serialized data in the cache_form of the database.

Any guidance or tips are very appreciated as the problem is certainly elusive.

If it is helpful I did recently do some module updates to make the system secure. But as stated above this problem only happens with very few modules active: Ubercart + CCK + Imagefield/filefield active.

Thanks!

I also tried just now creating a 1x1 px default image, setting it in the imagefield settings of the content to see if it would change things, but it doesn't. It lists the defaultimage in the serialized data, but then it still produces gigantic amounts of data beneath it (no change in percievable size).

If I could just get clarity/clarification that the unending data that reads above like is indeed an "image" then at least I know for sure this is the bug/problem:

...1;b:0;i:32;b:0;i:33;b:0;i:34;b:0;i:35;b:0;i:36;b:0;i:37;b:0;i:38;b:0;i:39
;b:0;i:40;b:0;i:41;b:0;i:42;b:0;i:43;b:0;i:44;b:0;i:45;b:0;i:46;....

Is this data for a default image? Is it "normal" to have this data when no image is added at all, and none is specified? I'll have to try a fully-clean drupal install but maybe someone already knows the answer as now I need to switch gears back to another client/project for a short while.

Thanks quickstretch.

BTW maybe off topic, but when I am debugging PHP in eclipse I can track variables but is there any way to track/trigger on the *size* of a variable instead of a value? It would make finding the point at which it inflates a lot easier considering how many functions there are to step through and debug.

Do you know if the other cases also had ubercart installed? When I read the referred cases it doesn't seem to be the case.

In the meantime I will try and uninstall all the modules and update them with latest and/or dev versions to see if somehow somewhere a bug was resolved or created -- but at this point I still feel like I'm shooting in the dark.

Good to know that there shouldn't be any binary data in the cache_form, seems like some kind of variable mismatch then where something is being written to the serialized cache form when it shouldn't be.

Also would it be useful for you if I simplified the system down to barebasics (garland theme etc.) and provided the code so that you can actually see a reproducible instance of the issue? I only offer this because you mentioned in one of the tickets that you have never been able to see or re-recreate the issue.

Sincerely,

Seb.

Okay great, I have to deal with some other web-items first and then I will see if I can remove all the sensitive information from this website so that it is as bare-bones as possible. May take me a day or two to make the time for it.

I'll also get you the PHP version, anything else you might want to know?

Kindly,

Seb.

Translation of #11 by emena, for non-french speakers:

Sorry, I do not write in english.

I have the same problem with image field.
Everything is fine when I don't use it, but as soon as I turn it on, I have memory problems.

I need at least 196M of cache for PHP, my pages take 30s to generate and use 120M.