6.0.0-git
2019-03-20

[#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 2011-05-10 (2871 days ago)
Due
Updated 2011-05-23 (2858 days ago)
Assigned
Resolved 2011-05-20 (2861 days ago)
Milestone
Patch No

History
2011-05-23 12:45:13 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.
2011-05-20 13:34:52 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.
2011-05-10 09:04:54 alessandro (dot) dellavedova (at) gmail (dot) com Comment #1
Type ⇒ Bug
State ⇒ Unconfirmed
Priority ⇒ 2. Medium
Summary ⇒ Memory exhausted in turba/lib/Driver/Ldap.php on line 520
Queue ⇒ Turba
Milestone ⇒
Patch ⇒ No
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

Saved Queries