PHP loop when flexifield set to current content type

I have exactly the same problem on shared webhost, where I can use up to 40M memory (which is quite generous for shared host, I think).

Me too... I'm using the alpha2 version.

I just discovered what was happening, and it was my mistake.
I was trying to crate a flexi-field for the content type "A" and I was selecting the same "A" content type as field item.

I would suggest not to let choosing the same content type in which you are to avoid this recursive bug.

Leo

I experienced the exact same affect.

Steps needed to reproduce "Memory error":

1. Create new content type. (i.e. "Foo")
2. Create a new flexifield field for Foo.
3. Check "Foo" under "Content types that can be used as field items:"

This will cause the script to loop, exhausting all available memory.

I agree it's "silly mistake" to be made, but can easily be avoided by simply not allowing the user to include the content type.

Hi all, in case anyone here hasn't read my status update on the project page, I wanted to say that I apologize for not having maintained this module well for the past couple months. I've been busy helping out on Drupal 7 core development. The code freeze for that was originally scheduled for 10/15, then extended to 10/19, we hit a snag on a couple important issues, and are now waiting for Dries to announce what is to happen to them. I'm pleased with what everyone has been able to accomplish with Drupal 7 prior to the freeze, and with my small contributions to it. I will be resuming maintenance on flexifield within the next couple days. Thank you for your patience.

thanks for the patch but can you please explain the second part of it

@@ -675,4 +680,4 @@ function template_preprocess_flexifield_
       }
     }
   }
-}
\ No newline at end of file
+}