[Tickets #14453] Re: Allowed memory size exhausted

[noreply at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: https://bugs.horde.org/ticket/14453
------------------------------------------------------------------------------
  Ticket             | 14453
  Updated By         | Michael Rubinsky <mrubinsk at horde.org>
  Summary            | Allowed memory size exhausted
  Queue              | Kronolith
  Version            | 4.2.17
  Type               | Bug
  State              | Assigned
  Priority           | 2. Medium
  Milestone          |
  Patch              |
  Owners             | Michael Rubinsky
------------------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2016-08-26 14:36) wrote:

> I don't think it is resolved for when an alarm is set.
>
> In the Kronolith_Driver_Sql::listAlarms, listEvents is called  
> without an endDate parameter... Then in  
> Kronolith_Driver_Sql::_listEvents, addEvents is called without this  
> parameter too. So the loop doesn't stop before the original event's  
> end date...

The reason this works is because if no $endDate is passed to  
addEvents, then the check $loopDate->compareDateTime($endDate) returns  
false, thus breaking the loop.

I still can't get the stable code (FRAMEWORK_5_2) to break with this  
patch. However, I AM having problems with the git master code at the  
moment.