[Tickets #14745] Re: Horde_Mapi winmail.dat file of 800kB produces memory leak

noreply at bugs.horde.org noreply at bugs.horde.org
Mon Dec 4 08:32:37 UTC 2017


BITTE NICHT AUF DIESE NACHRICHT ANTWORTEN. NACHRICHTEN AN DIESE  
E-MAIL-ADRESSE WERDEN NICHT GELESEN.

Ticket-URL: https://bugs.horde.org/ticket/14745
------------------------------------------------------------------------------
  Ticket           | 14745
  Aktualisiert Von | admin at layertec.de
  Zusammenfassung  | Horde_Mapi winmail.dat file of 800kB produces memory leak
  Warteschlange    | IMP
  Version          | Git master
  Typ              | Bug
  Status           | Feedback
  Priorität        | 1. Low
  Milestone        |
  Patch            |
  Zuständige       |
------------------------------------------------------------------------------


admin at layertec.de (2017-12-04 08:32) hat geschrieben:

>>> This is not a memory leak, technically.
>>> Can you provide an example message?
>>
>> Didn't I?
>>
>> 2017-12-01T15:48:36+01:00 EMERG: HORDE [imp] Allowed memory size of
>> 11610612736 bytes exhausted (tried to allocate 1207959552 bytes) [pid
>> 15047 on line 1090 of "/usr/share/php/Math/BigInteger.php"]
>
> Not an error message, but an email message (or winmail.dat file),  
> that triggers this behaviour ;-)
>
>> I wonder, if imap or the Horde_Mapi extension might use php_bcmath
>> instead of PEAR math, if it is installed?
>
> Yes, it does.

Unfortunately the email message is confidential, sorry.

In the meantime, I found another ticket that seems to mention the same  
issue. It says it is not a bug in IMP or Horde_Mapi but the  
BigInteger-Implementation of PEAR. I just tried to install php-bcmath  
(7.0.19-1) and it seems to work fine now.

It's just a bit hard to figure out the behaviour when there are  
multiple possible implementations.

I learned to get rid of PEAR implementations wherever possible.

The issue is solved for me now.





More information about the bugs mailing list