"Unable to allocate memory for pool" error - fixed?

[Jonathan Robie]

I think the ibiblio staff have fixed the following error, which was occurring frequently:

Code: Select all

[phpBB Debug] PHP Notice: in file /search.php on line 271: require()
[function.require]: Unable to allocate memory for pool.
[phpBB Debug] PHP Notice: in file /search.php on line 525: include()
[function.include]: Unable to allocate memory for pool.

Is anyone still seeing this error?

[Stephen Carlson]

I just got one when I went to my login page.

[Jonathan Robie]

I just got one when I went to my login page.

Thanks - I'll report this. They are working on it ...

[Jonathan Robie]

Sigh. I'm getting them again now too...

[Jason Hare]

Looks good on my android.

[Jonathan Robie]

It's looking good to me again now too. I hate intermittent errors!

[Jason Hare]

It just came back. Ugh.

[Jason Hare]

Cleared up again, by the way.

[Jonathan Robie]

Hopefully permanently. If you see any more errors, please mention that here.

Here's what ibiblio said about this:

Hey Jonathan,

Here's a summary of what has happened and what I have done:

1) APC was originally caching everything/php on ibiblio.org. The cache
was relatively small, and you'd get those nice out of memory errors when
it filled up.

2) I disabled, or rather, thought I had disabled APC for everything in
/public/html/bgreek. You kept getting memory errors.

3) I tweaked the caching settings and memory limits in APC and php.
Things were good for a time, and then you saw memory errors again. The
cache filled up.

4) I have just now disabled APC in a different manner (poor
documentation), after trying out half a dozen methods. I have confirmed
that nothing in /public/html/bgreek is making it into the APC cache.

So you should be set. I know this is the fourth time I've said that,
but it is also the fourth time I expected it. I don't see any bgreek
items in the cache though! Apologies for the run-around

Also, if you were curious as to why the memory errors were so difficult
to replicate (especially now, after I have tweaked the cache), it is
because two pieces of this puzzle - or rather, 6 - are variable.
ibiblio.org is handled by three servers, and each of those servers have
APC installed. So you could be hitting any of those servers with any
given request, and each have an APC that may have a full cache one
minute, but not the next.

[Stephen Carlson]

Intermittent errors are the hardest computer bugs to fix!