Summary | Memory Exhausted when replying some messages |
Queue | IMP |
Queue Version | 6.0.3 |
Type | Bug |
State | Resolved |
Priority | 2. Medium |
Owners | slusarz (at) horde (dot) org |
Requester | david.fernandez (at) ehu (dot) es |
Created | 01/14/2013 (4550 days ago) |
Due | |
Updated | 01/14/2013 (4550 days ago) |
Assigned | |
Resolved | 01/14/2013 (4550 days ago) |
Github Issue Link | |
Github Pull Request | |
Milestone | |
Patch | No |
Assigned to Michael Slusarz
State ⇒ Resolved
commit 040950dacbdebc2659f21cc72318ce0727b8623c
Author: Michael M Slusarz <slusarz@horde.org>
Date: Mon Jan 14 13:04:09 2013 -0700
[mms] Workaround broken Message-IDs generated by Outlook when
replying to a message (
Bug #11953).imp/docs/CHANGES | 2 +
imp/lib/Compose/References.php | 37 ++++++++++++++++++++++++++++++++-
imp/package.xml | 2 +
imp/test/Imp/Unit/ReferencesTest.php | 18 ++++++++++++++++
4 files changed, 57 insertions(+), 2 deletions(-)
http://git.horde.org/horde-git/-/commit/040950dacbdebc2659f21cc72318ce0727b8623c
sometimes generate invalid Message-ID for e-mails. This Message-ID
contains 2 '@'.
In these cases, IMP generates al infinite loop that exhausted memory
of PHP process..
More info:
http://www.outlookforums.com/threads/17887-outlook-2007-generates-illegal-message-id/
Priority ⇒ 2. Medium
Patch ⇒ No
Milestone ⇒
Queue ⇒ IMP
Due ⇒ 01/14/2013
Summary ⇒ Memory Exhausted when replying some messages
Type ⇒ Bug
State ⇒ Unconfirmed
exhausted. The error that appears in Apache's error_log could be:
PHP Fatal error: Allowed memory size of 115343360 bytes exhausted
(tried to allocate 32 bytes) in
/users/bcwhord5/public_html/pear/php/Horde/Mail/Rfc822.php on line
795, referer:
https://dev.ehu.es/wpostapiloto/imp/dynamic.php?page=mailbox
or:
PHP Fatal error: Allowed memory size of 115343360 bytes exhausted
(tried to allocate 71 bytes) in
/users/bcwhord5/public_html/imp/lib/Compose/References.php on line 51,
referer: https://dev.ehu.es/wpostapiloto/imp/dynamic.php?page=mailbox
I increase the memory in php.ini to 2GB and the problem persists.
I tried with IMP 6.0.2 and the same messages and it works.
The error occurs in basic and dynamic mode.