Tickets :: [#10064] Memory exhausted in turba/lib/Driver/Ldap.php on line 520

Summary	Memory exhausted in turba/lib/Driver/Ldap.php on line 520
Queue	Turba
Queue Version	3.0.2
Type	Bug
State	Not A Bug
Priority	2. Medium
Owners
Requester	alessandro.dellavedova (at) gmail (dot) com
Created	05/10/2011 (5147 days ago)
Due
Updated	05/23/2011 (5134 days ago)
Assigned
Resolved	05/20/2011 (5137 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

05/23/2011 12:45:13 PM	alessandro (dot) dellavedova (at) gmail (dot) com	Comment #3	Reply to this comment
This doesn't necessarily have anything to do with Turba. The code just happens to run something in Turba while the memory is exhausting. Raise your memory limit. I have raised the PHP memory_limit from 128MB to 256MB and now it works but I'm concerned about the scalability, since now I'm the only user testing the Horde/IMP/Kronolith/Turba suite on this server, but when rolling into production I will have more or less 500 users to accomodate on this server that has 16GB of RAM.

05/20/2011 01:34:52 PM	Jan Schneider	Comment #2 State ⇒ Not A Bug	Reply to this comment
This doesn't necessarily have anything to do with Turba. The code just happens to run something in Turba while the memory is exhausting. Raise your memory limit.

05/10/2011 09:04:54 AM	alessandro (dot) dellavedova (at) gmail (dot) com	Comment #1 Priority ⇒ 2. Medium Patch ⇒ No Milestone ⇒ Queue ⇒ Turba Summary ⇒ Memory exhausted in turba/lib/Driver/Ldap.php on line 520 Type ⇒ Bug State ⇒ Unconfirmed	Reply to this comment
I configured Turba in order to read my contacts from our centralized LDAP directory (~1000 entries) and it seems to work fine. The problem arises under IMP, when I double click on one message from my IMAP Inbox (~13000 messages) , a separate message window is opened but it contains the following message: Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 982533 bytes) in <SNIP>/horde/turba/lib/Driver/Ldap.php on line 520