6.0.0-beta1
7/27/25

[#3743] Out of memory when listing users
Summary Out of memory when listing users
Queue Horde Framework Packages
Queue Version FRAMEWORK_3
Type Bug
State Not A Bug
Priority 2. Medium
Owners
Requester rajkumars (at) asianetindia (dot) com
Created 04/07/2006 (7051 days ago)
Due
Updated 04/08/2006 (7050 days ago)
Assigned
Resolved 04/08/2006 (7050 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
04/08/2006 09:17:33 AM Jan Schneider Comment #3
State ⇒ Not A Bug
Reply to this comment
You should not use user listings with 14000 users, because this simply 
doesn't scale in Horde. And if you have 14000 users, you probably have 
a separate user management interface anyway. Don't misunderstand, 
Horde itself scales well, just not the user listings, for example in 
the share interfaces.

If you want to extend Horde to support such large listings or improve 
Horde's user managment, file an enhancement request.
04/08/2006 12:43:08 AM kmmyer (at) gmail (dot) com Comment #2 Reply to this comment
If you have any intention of using Horde for anything, with 14,000 
users, you're definitely going to have to give PHP more than 8MB of 
memory...



Although I agree that some sort of pagination is usually helpful for 
large arrays of elements, rather than presenting the user with a 
loooong list..
04/07/2006 01:37:43 PM rajkumars (at) asianetindia (dot) com Comment #1
State ⇒ Unconfirmed
Priority ⇒ 2. Medium
Type ⇒ Bug
Summary ⇒ Out of memory when listing users
Queue ⇒ Horde Framework Packages
Reply to this comment
Hi,



I am using horde-3.1.1 with qmail-ldap and fedora ldap server. I have 
about 14,000 users inthe ldap directory. When I click Administration 
-> Users,  nothing comes. Looking at apache error logs, I get a message:

Allowed memory size of 8388608 bytes exhausted (tried to allocate 12 bytes)



The ldap query is



SRCH base="o=isp" scope=2 filter="(&(objectClass=qmailuser))" attrs="uid"



which would return all 14,000 users. It seems php gets out of memory 
error when it is trying to process all the users at once. An obvious 
solution would be to limit the number of records fetched at once.


Saved Queries