DMS Possible Memory Leak?

[tlp6191]

When I use a normal account with DMS access to search for files, or open folders with very large (several thousand) documents, the session runs out of memory, tells me:
Fatal error: Allowed memory size of 524288000 bytes exhausted (tried to allocate 7680 bytes) in /var/www/egroupware/phpgwapi/inc/class.egw_db.inc.php(1962) : runtime-created function on line 1
and maybe spits out documents (Maybe all the documents, maybe just some. It’s hard to tell)

However, when I give the group for that user admin power, the problem goes away.
If I increase the PHP memory limit, the memory usage simply increases until I restart apache2 or the server simply freezes.

Right now, we have most users running with admin powers, which is unacceptable in the long run. Any ideas? Need more info?

Info: Egroupware 1.6
Ubuntu 8.04
PHP:
memory_limit = 500M ; Maximum amount of memory a script may consume (32MB)

[DonB-2]

I’m having similar issues with memory allocation problems. After about 10 minutes into a session, the system freezes and I get a very similar fatal error. Different file names and different lines.

I never had this issue with v1.4. I’ve posted a couple of times on this and you can see more responses by doing a search on “Fatal Error”. I don’t believe just increasing the memory limit in php.ini is the problem when v1.4 ran fine with default PHP settings.

In any case, maybe someone will finally take a harder look at this. This not the kind of stuff to keep lingering as it will push people away from the product (as I am starting to consider).

Cheers,
Don

When I use a normal account with DMS access to search for files, or open folders with very large (several thousand) documents, the session runs out of memory, tells me:
Fatal error: Allowed memory size of 524288000 bytes exhausted (tried to allocate 7680 bytes) in /var/www/egroupware/phpgwapi/inc/class.egw_db.inc.php(1962) : runtime-created function on line 1
and maybe spits out documents (Maybe all the documents, maybe just some. It’s hard to tell)

However, when I give the group for that user admin power, the problem goes away.
If I increase the PHP memory limit, the memory usage simply increases until I restart apache2 or the server simply freezes.

Right now, we have most users running with admin powers, which is unacceptable in the long run. Any ideas? Need more info?

Info: Egroupware 1.6
Ubuntu 8.04
PHP:
memory_limit = 500M ; Maximum amount of memory a script may consume (32MB)

[DonB-2]

I’m having similar issues with memory allocation problems. After about 10 minutes into a session, the system freezes and I get a very similar fatal error. Different file names and different lines.

I never had this issue with v1.4. I’ve posted a couple of times on this and you can see more responses by doing a search on “Fatal Error”. I don’t believe just increasing the memory limit in php.ini is the problem when v1.4 ran fine with default PHP settings.

In any case, maybe someone will finally take a harder look at this. This not the kind of stuff to keep lingering as it will push people away from the product (as I am starting to consider).

Cheers,
Don

When I use a normal account with DMS access to search for files, or open folders with very large (several thousand) documents, the session runs out of memory, tells me:
Fatal error: Allowed memory size of 524288000 bytes exhausted (tried to allocate 7680 bytes) in /var/www/egroupware/phpgwapi/inc/class.egw_db.inc.php(1962) : runtime-created function on line 1
and maybe spits out documents (Maybe all the documents, maybe just some. It’s hard to tell)

However, when I give the group for that user admin power, the problem goes away.
If I increase the PHP memory limit, the memory usage simply increases until I restart apache2 or the server simply freezes.

Right now, we have most users running with admin powers, which is unacceptable in the long run. Any ideas? Need more info?

Info: Egroupware 1.6
Ubuntu 8.04
PHP:
memory_limit = 500M ; Maximum amount of memory a script may consume (32MB)