# Allowed memory exhausted

**URL:** <http://discourse.egroupware.org/t/allowed-memory-exhausted/31866>\
**Category:** eGW-users\
**Created:** [May 5, 2009, 3:21pm UTC](http://discourse.egroupware.org/t/allowed-memory-exhausted/31866 "2009-05-05T15:21:13Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![nemethz](http://discourse.egroupware.org/letter_avatar_proxy/v4/letter/n/9fc348/32.png) [@nemethz](http://discourse.egroupware.org/u/nemethz)\
**Post date:** [May 5, 2009, 3:21pm UTC](http://discourse.egroupware.org/t/allowed-memory-exhausted/31866/1 "2009-05-05T15:21:13Z")

</div>

Hi,  
After modifying 10 entries in addressbook I get the following error in log:  
[05-May-2009 14:37:28] PHP Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 785825 bytes) in Unknown on line 0  
I can do any further editing after logging out and then in.  
If I change the PHP memory\_limit option from 64M to 128M, then I can edit 15 entries before it is blocked.  
My environment:

- eGroupware 1.6.001
- PHP 5.2.0
- openSuSE 10.2  
Thank you for your answer in advance.  
Regards, Zoltán Németh

---

<div class="post-metadata">

**Author:** ![DonB-2](http://discourse.egroupware.org/letter_avatar_proxy/v4/letter/d/bb73d2/32.png) [@DonB-2](http://discourse.egroupware.org/u/DonB-2)\
**Post date:** [May 6, 2009, 12:47am UTC](http://discourse.egroupware.org/t/allowed-memory-exhausted/31866/2 "2009-05-06T00:47:53Z")

</div>

It’s most likely a PHP bug. PHP 5.2.9 is out now and the very irritating memory leaks seems to have been resolved.

I had been receiving chronic memory errors since upgrading EGW to 1.6. Then, another web-app started suffering from the same errors.

After doing a google search on PHP and memory leaks, it was discovered PHP has had a running history of this problem.

I had PHP 5.2.3. Now with 5.2.9, everything seems to be peachy.

Cheers,  
Don

> [@](#):
>
> Hi,  
> After modifying 10 entries in addressbook I get the following error in log:  
> [05-May-2009 14:37:28] PHP Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 785825 bytes) in Unknown on line 0  
> I can do any further editing after logging out and then in.  
> If I change the PHP memory\_limit option from 64M to 128M, then I can edit 15 entries before it is blocked.  
> My environment:
> 
> - eGroupware 1.6.001
> - PHP 5.2.0
> - openSuSE 10.2  
> Thank you for your answer in advance.  
> Regards, Zoltán Németh

---

<div class="post-metadata">

**Author:** ![htbt13](http://discourse.egroupware.org/letter_avatar_proxy/v4/letter/h/a8b319/32.png) [@htbt13](http://discourse.egroupware.org/u/htbt13)\
**Post date:** [May 6, 2009, 12:48pm UTC](http://discourse.egroupware.org/t/allowed-memory-exhausted/31866/3 "2009-05-06T12:48:18Z")

</div>

Hi,

may be its the Parameter php\_value\_limit in your .htaccess file.

Herbert

> [@](#):
>
> It’s most likely a PHP bug. PHP 5.2.9 is out now and the very irritating memory leaks seems to have been resolved.
> 
> I had been receiving chronic memory errors since upgrading EGW to 1.6. Then, another web-app started suffering from the same errors.
> 
> After doing a google search on PHP and memory leaks, it was discovered PHP has had a running history of this problem.
> 
> I had PHP 5.2.3. Now with 5.2.9, everything seems to be peachy.
> 
> Cheers,  
> Don
> 
> > [@](#):
> >
> > Hi,  
> > After modifying 10 entries in addressbook I get the following error in log:  
> > [05-May-2009 14:37:28] PHP Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 785825 bytes) in Unknown on line 0  
> > I can do any further editing after logging out and then in.  
> > If I change the PHP memory\_limit option from 64M to 128M, then I can edit 15 entries before it is blocked.  
> > My environment:
> > 
> > - eGroupware 1.6.001
> > - PHP 5.2.0
> > - openSuSE 10.2  
> > Thank you for your answer in advance.  
> > Regards, Zoltán Németh

---

<div class="post-metadata">

**Author:** ![nemethz](http://discourse.egroupware.org/letter_avatar_proxy/v4/letter/n/9fc348/32.png) [@nemethz](http://discourse.egroupware.org/u/nemethz)\
**Post date:** [May 6, 2009, 8:15pm UTC](http://discourse.egroupware.org/t/allowed-memory-exhausted/31866/4 "2009-05-06T20:15:56Z")

</div>

Hi,  
I set the php\_value memory\_limit but it was not a help.  
Thank you.  
Zoltán

> [@](#):
>
> Hi,
> 
> may be its the Parameter php\_value\_limit in your .htaccess file.
> 
> Herbert
> 
> > [@](#):
> >
> > It’s most likely a PHP bug. PHP 5.2.9 is out now and the very irritating memory leaks seems to have been resolved.
> > 
> > I had been receiving chronic memory errors since upgrading EGW to 1.6. Then, another web-app started suffering from the same errors.
> > 
> > After doing a google search on PHP and memory leaks, it was discovered PHP has had a running history of this problem.
> > 
> > I had PHP 5.2.3. Now with 5.2.9, everything seems to be peachy.
> > 
> > Cheers,  
> > Don
> > 
> > > [@](#):
> > >
> > > Hi,  
> > > After modifying 10 entries in addressbook I get the following error in log:  
> > > [05-May-2009 14:37:28] PHP Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 785825 bytes) in Unknown on line 0  
> > > I can do any further editing after logging out and then in.  
> > > If I change the PHP memory\_limit option from 64M to 128M, then I can edit 15 entries before it is blocked.  
> > > My environment:
> > > 
> > > - eGroupware 1.6.001
> > > - PHP 5.2.0
> > > - openSuSE 10.2  
> > > Thank you for your answer in advance.  
> > > Regards, Zoltán Németh

---

<div class="post-metadata">

**Author:** ![nemethz](http://discourse.egroupware.org/letter_avatar_proxy/v4/letter/n/9fc348/32.png) [@nemethz](http://discourse.egroupware.org/u/nemethz)\
**Post date:** [May 6, 2009, 8:24pm UTC](http://discourse.egroupware.org/t/allowed-memory-exhausted/31866/5 "2009-05-06T20:24:15Z")

</div>

Hi,  
I think the PHP 5.2.9 might be a help. I am afraid of installing PHP 5.2.9 because the openSuSE updates does not contain it yet.  
Regards,  
Zoltán

> [@](#):
>
> It’s most likely a PHP bug. PHP 5.2.9 is out now and the very irritating memory leaks seems to have been resolved.
> 
> I had been receiving chronic memory errors since upgrading EGW to 1.6. Then, another web-app started suffering from the same errors.
> 
> After doing a google search on PHP and memory leaks, it was discovered PHP has had a running history of this problem.
> 
> I had PHP 5.2.3. Now with 5.2.9, everything seems to be peachy.
> 
> Cheers,  
> Don
> 
> > [@](#):
> >
> > Hi,  
> > After modifying 10 entries in addressbook I get the following error in log:  
> > [05-May-2009 14:37:28] PHP Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 785825 bytes) in Unknown on line 0  
> > I can do any further editing after logging out and then in.  
> > If I change the PHP memory\_limit option from 64M to 128M, then I can edit 15 entries before it is blocked.  
> > My environment:
> > 
> > - eGroupware 1.6.001
> > - PHP 5.2.0
> > - openSuSE 10.2  
> > Thank you for your answer in advance.  
> > Regards, Zoltán Németh