CBConditional file triggers PHP Fatal Error (allowed memory exhausted) when users with many profile fields update their profile

Dear,

We use cbconditional plugin to manage the tabs of the user profile during registration and profile view/edit. We have different user types based on the value of one field ('usertype'), and do all kinds of conditional showing/hiding of fields and tabs on the profile and the registration based on this value.

Now, there seems to be a problem with the user type that has most tabs+fields visible+editable: when such a user goes to his own profile, goes in edit mode, and submits the form to update his profile, we get a PHP fatal 'memory exhausted' error:

Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 523800 bytes) in <span>/</span>var<span>/</span>www/html/components/com_comprofiler/plugin/user/plug_cbconditional/cbconditional.class.php on line 71

Changing the allowed memory in php.ini or with an ini_set does not make a difference (we tried both raising the limit to 128/256/...MB and setting to -1), so my best guess is a MySQL query going wrong or something when there's too many fields.

Haven't been able to make much more sense of it by looking / echo'ing inside the file mentioned in the error though.

(we use CB 1.9 with CBConditional plugin version 3.0.

Kind regards and thanks in advance. If you would like to have a look at our CB field configuration, feel free to ask and we'll get you an admin account.

The more fields you condition the heavier it's going to get. So for example if you condition 100 fields at once that's a lot to process though.

With that said there is some fields that can cause memory loop issues. For example never condition a field that has no profile edit display with a profile edit condition. An example scenario is the CB Progress Field; if you condition it on Profile Edit it'll cause problems and should only be conditioned in Profile View.

Please also note you're using an out of date CB Conditional so you may be experiencing an already fixed bug. Please upgrade to 3.0.12 (latest).