Tickets :: [#1405] PGP/MIME signed messages do not display (memory exhausted)

6.0.0-beta1

7/10/25

Summary	PGP/MIME signed messages do not display (memory exhausted)
Queue	IMP
Queue Version	4.0.2
Type	Bug
State	Resolved
Priority	1. Low
Owners
Requester	sweetpea-horde (at) tentacle (dot) net
Created	02/18/2005 (7447 days ago)
Due
Updated	07/31/2005 (7284 days ago)
Assigned	02/18/2005 (7447 days ago)
Resolved	07/31/2005 (7284 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

07/31/2005 09:52:15 PM	Chuck Hagenbuch	State ⇒ Resolved

07/31/2005 09:42:40 PM	t (dot) zell (at) gmx (dot) de	Comment #11	Reply to this comment
... and gone with horde-3.0.5-rc2

07/31/2005 02:10:19 PM	t (dot) zell (at) gmx (dot) de	Comment #10	Reply to this comment
Same problem here: php 5.0.3 horde 3.0.4 imp 4.0.3

03/14/2005 02:42:47 AM	Michael Slusarz	Comment #9	Reply to this comment
This reinforces the suggestion that you have a badly broken PHP or PHP component.

03/13/2005 07:25:39 PM	dkowis (at) shlrm (dot) org	Comment #8	Reply to this comment
I've got a similar problem also associated with viewing gpg signed messages: in error_log: FATAL: erealloc(): Unable to allocate 2037542955 bytes FATAL: erealloc(): Unable to allocate 1953850144 bytes

03/07/2005 12:51:23 PM	Jan Schneider	State ⇒ Stalled

03/07/2005 01:01:29 AM	sweetpea-horde (at) tentacle (dot) net	Comment #7	Reply to this comment
This has not happened recently. I don't have any accelerators or any odd settings, just using PHP 5.0.3, which would be hard to change at the moment. I'll post if I find any more information.

03/06/2005 12:46:35 PM	Jan Schneider	Comment #6	Reply to this comment
This has to be a local issue on your system, other we would see that happen too. Try disabling any PHP accelerators that you might use, try a different PHP version etc.

02/19/2005 09:26:27 AM	sweetpea-horde (at) tentacle (dot) net	Comment #5	Reply to this comment
I am sometimes able to view such messages, too. It seems to happen mostly with GPG-signed messages that I send. I can send you a message personally, which you could try viewing, and see if your version has the same problems.

02/18/2005 10:04:25 AM	Jan Schneider	Comment #4 State ⇒ Feedback	Reply to this comment
I can view this message fine, after I fixed the broken header folding, with a memory_limit of 128M.

02/18/2005 09:16:05 AM	sweetpea-horde (at) tentacle (dot) net	Comment #3 New Attachment: sample-message.txt	Reply to this comment
The message is tiny, < 1k. Here's the [edited] message source of one example (attached).

02/18/2005 06:52:27 AM	Michael Slusarz	Comment #2	Reply to this comment
How big is this message? Because I have no idea how Horde would be trying to allocate 1.7 GB for a single message. And I don't think the answer is infinite recursion either - PHP will segfault long before it produces an error message. I have never seen this problem, BTW, even with PGP messages of several MB.

02/18/2005 01:13:15 AM	sweetpea-horde (at) tentacle (dot) net	Comment #1 Priority ⇒ 1. Low Type ⇒ Bug Summary ⇒ PGP/MIME signed messages do not display (memory exhausted) Queue ⇒ IMP State ⇒ Unconfirmed	Reply to this comment
When viewing OpenPGP/MIME signed messages, instead of the usual display, the page load just stops. In the http error log, the following message appears: PHP Fatal error: Allowed memory size of 16777216 bytes exhausted (tried to allocate 1702065101 bytes) in /u0/httpd/horde/lib/Horde/SessionObjects.php on line 134, referer: The exact number of bytes it tries to allocate changes with each request, but it's always close to that number. If I reload the page several times, it generally displays, though it still logs that error most (but not all) of the time.