PHP Memory Limit debugging

Question

I have a client with a Wordpress site. They are running a couple of plugins which are causing Fatal Memory errors. The 2 plugins specifically are Simple Map & Drain Hole.I am not sure which of these plugins exactly is causing the issue. Simple Map is used to manage locations or providers, much like Google Places. Drain Hole is used to protect files via URL cloaking.

Within Simple Map, they currently have about 900 locations. Within Drain Hole they currently have about 700 files protected. During development, we had no issues whatsoever, as our PHP memory limit was set to 64MB. On their live server, the host only allows 30MB, and will not allow this to be changed.

My issue/question is this: If I move them to a new host, one that allows atleast 64MB, how can I be sure that if they continue to add to those plugins, that this will not happen again? Is there anyway to test if these memory spikes are legitimate, or if they are a result of poor, inefficient code?

EDIT: The fatal error seems to be hit or miss. It only happens in certain screens of the Wordpress Admin panel, specifically those dealing with Simple Map. Although if I disable the Drain Hole plugin, the error goes away completely. The error:

**Fatal error:** Out of memory (allocated 34078720) (tried to allocate 44 bytes) in /fake/dir/wp-includes/wp-db.php on line 1400

Is your host only blocking you from editing your php.ini? If so can you set the memory in the script using ini_set('memory_limit', 64);? — Parris Varney
– Parris Varney, Commented Apr 13, 2011 at 14:37
They have blocked it completely. I have tried several methods to increase the limit. Hosting is currently with 1and1 (Who I hate) — Chris
– Chris, Commented Apr 13, 2011 at 14:40

markratledge · Accepted Answer · 2011-04-14 04:26:00Z

2

1and1 is notorious for being a bad WP host. WP 3.1 tries to allocate 64megs to itself when run, and in wp-config.php, you can add this line near the top

define('WP_MEMORY_LIMIT', '128M');

to grab more, if a host allows it. Find a new host, if possible. You're running plugins in an intensive manner that will require that much RAM. It may be a fault of the plugins and of WP, but that's the way it is.

answered Apr 14, 2011 at 4:26

markratledge

17.6k12 gold badges65 silver badges108 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Chris Over a year ago

Yes, I am moving to a new host, as 1and1 does not allow us to have more then 30MB without moving to dedicated.

jonshariat · Accepted Answer · 2011-04-13 19:52:49Z

0

I know that this happens with buggy plug-ins. Unfortunately, it takes turning them off one by one, to see which plug-in is to blame. But after that plug-in is deactivated, you will be fine.

That was my solution when I received that same error.

answered Apr 13, 2011 at 19:52

jonshariat

1743 silver badges16 bronze badges

1 Comment

Chris Over a year ago

I would agree that this is the solution in certain cases. However, in this case, the plugins are actually needed, and technically run fine. I have a feeling in this case, the amount of data which these plugins are controlling is more then expected, which is the cause of the memory spikes in certain pages

Collectives™ on Stack Overflow

PHP Memory Limit debugging

2 Answers 2

1 Comment

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

1 Comment

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related