Fatal Errors in CP After upgrading from 2.x to 3.3.3 - Allowed Memory Size xxxxx exhausted

Are you adding a large member group to the author list perhaps?

Are you adding a large member group to the author list perhaps?

Hi Derek,

I’m having the same issue – we have about 1400 members and I’m adding them to the author list. We’re getting a Fatal Error in CP when editing due to Memory Exhausted.

We’re also getting the same Fatal Error when editing an entry with a Relationship field pulling from a channel with around 1200+ entries.

Checked with the server and we’re at our max memory of 99M. Any way to fix this?

Thanks! Shaun

What version of ExpressionEngine are you on, cozmir?

Adding that many members to the author list is not practical, even without exhausting memory. Scrolling through a dropdown of 1400 members would not be very usable. May I ask what the reason is for needing to add this many members to the author list dropdown?

We’re on ExpressionEngine 3.3.3.

The practicality is fine actually, since we’re actually not scrolling through them - we’re using the User plugin to use a Related Authors field. It allows us to give permissions to those in the member list to see certain entries.

Gotcha. The author list simply isn’t designed to hold that many options—you might consider something like Vector’s Chosen Member field type, it’s made for pretty much exactly what you’re looking for.

You definitely should not be hitting memory errors on native relationship fields, their data is return-limited and filterable. If you have a reproducible issue there, please submit a support request or a bug report and we’ll help you get to the bottom of it.

Thanks Derek, appreciate the recommendation - I’ll look into Chosen Member and give it a shot.

I’ll also retry the relationship field and submit a request if I continue to have issues.

Gotcha. The author list simply isn’t designed to hold that many options—you might consider something like [Vector’s Chosen Member field type](https://github.com/vector/VMG-Chosen-Member), it’s made for pretty much exactly what you’re looking for. You definitely should not be hitting memory errors on native relationship fields, their data is return-limited and filterable. If you have a reproducible issue there, please submit a support request or a bug report and we’ll help you get to the bottom of it.

Hi Derek,

I looked into the VMG Chosen Member add-on, but it looks like it’s for EE 2 - do you know if anyone has modified it or if there’s something similar that’s EE 3 compatible?

I ended up moving our installation over to a dedicated server and that helped relieve our memory issues for the relationship field. It’s still using 60MB to load the entry edit page though, does that seem high? It’s still a bit sluggish.

Appreciate the help!

Looks like their readme needs to be updated, but there is a branch for v3.

60M does seem high to me for a typical edit entry page. Chosen Member should alleviate that, as you aren’t loading in data for a thousand plus members at once. 10M is probably a mean for channels with many fields. Also impacting memory: what version of PHP are you currently on?

Oh, perfect! Thanks for sending the link to the branch for 3.

We’re running PHP Version 5.6.21.

5.6 is pretty good on memory. You’d have some performance gains moving to PHP 7, but I think it’s the member list in the drop down that’s choking things at the moment for you. At least in terms of which modification will provide the most gain.