Tickets :: Comment on [#14550] Decoding certain TNEF files results in memory exhaustion

* Your Email Address
* Spam protection	Enter the letters below: . . ..__ .___.. . \| \|\ \|[ __ \| \ / \|___\| \\|[_./ \| \/
Comment	> I have setup a new sync with a new device. But the only thing i see until the > > HORDE[5838]: Allowed memory size of 134217728 bytes exhausted (tried > to allocate 150994944 bytes) [pid 5838 on line 1090 of > "/usr/share/php/Math/BigInteger.php"] > > Can i send you the log file so you can have a look? I really can not > find anything :-( > >>>>> Do you have any hint where i can find the message maybe in the log >>>>> file? Unfortunately i do not now which mail is causing this. >>>> >>>> If you know which device it is at least, you can enable a per-device >>>> activesync debug log. It would be the last message attempted to be >>>> sent. >>>> >>>> If you don't know the device, you can instead try the consolidated >>>> debug log and hope we can figure it out from there. >>>> >>>> Looking at where the process dies, it is probably an email with some >>>> type of TNEF attachment. >>>> >>>> >>>>>> Please provide a sample email that triggers this error. >>>>> >>>> >>> >>> It looks like it is not dying but still trying to do the sync. >> >> Well, when the memory is exhausted, the running process dies and the >> sync must restart. >> >>> The only thing i can find is this error message: >>> >>> Previous request processing for synckey >>> {58608cf6-006c-4922-b379-4ed95e72af70}123 failed to be accepted by >>> the client, removing previous state and trying again. >> >> Correct. This indicates a previous attempt failed since the client is >> sending an older synckey. >> >>> The Client is Outlook 2016 >> >
Attachment
Watch this ticket

Saved Queries