| Summary | Recurrence::nextRecurrence(weekly) recursive function call |
| Queue | Horde Framework Packages |
| Queue Version | HEAD |
| Type | Bug |
| State | Not A Bug |
| Priority | 1. Low |
| Owners | |
| Requester | thomas.jarosch (at) intra2net (dot) com |
| Created | 3/6/08 (6610 days ago) |
| Due | |
| Updated | 5/26/08 (6529 days ago) |
| Assigned | 5/24/08 (6531 days ago) |
| Resolved | 5/26/08 (6529 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
State ⇒ Not A Bug
rather not want to change it. But if you could provide a test case to
reproduce the infinite loop we could try to track down what's going
wrong.
recurrence with 98949324892 recurrences. I've fixed that by
#6388,so I think we can leave the code as it is until we stumble
on it again with real data (which probably shouldn't happen).
Thomas
State ⇒ Feedback
not want to change it. But if you could provide a test case to
reproduce the infinite loop we could try to track down what's going
wrong.
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ Recurrence::nextRecurrence(weekly) recursive function call
Queue ⇒ Horde Framework Packages
State ⇒ Unconfirmed
during tests with the new Kolab freebusy framework I bombarded the
code with all kinds of calendering data. Suddenly PHP started
segfaulting.
It turned out this was due to a
Horde_Date_Recurrence::nextRecurrence() recursive function call for an
unlimited weekly recurrence which hit the internal stack size limit of
PHP. After adding a debug
counter I saw nextRecurrence() being called over 1.600 times.
Jan, as you are most familiar with the recurrence code,
would it be possible to change the recursive function call into a loop?
Cheers,
Thomas