| Summary | Yearly events cause memory exhausted exception |
| Queue | Kronolith |
| Queue Version | Git master |
| Type | Bug |
| State | Not A Bug |
| Priority | 1. Low |
| Owners | |
| Requester | joniw (at) t-online (dot) de |
| Created | 12/16/2011 (4959 days ago) |
| Due | |
| Updated | 01/26/2012 (4918 days ago) |
| Assigned | |
| Resolved | 01/26/2012 (4918 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
was fixe with one of the commits.
with regards
Jonathan Westerholt
duplicated there. After deleting the duplicated birthdays in outlook
and syncing with horde i am now able to login.
Perhabs the problem were the duplicated birthdays but the login still
takes some time to load the portal page. While loading the front page,
apache also takes 100% cpu so it looks like there could be some
optimizations on loading the events.
with regards
Jonathan Westerholt
Priority ⇒ 1. Low
Patch ⇒ No
Milestone ⇒
Queue ⇒ Kronolith
Summary ⇒ Yearly events cause memory exhausted exception
Type ⇒ Bug
State ⇒ Unconfirmed
them to horde i can not login anymore because the php script dies with:
PHP Fatal error: Allowed memory size of 268435456 bytes exhausted
(tried to allocate 75 bytes) in
/opt/horde-dev/git/kronolith/lib/Kronolith.php on line 690
Sometimes there are other lines mentioned but all are from the range
of the while-loop from line 687 til line 715.
It looks like there are a lot of objects created there. I also added a
debug output in the while loop to detect the number of rounds for one
yearly event. in some events the number gose up to 115.
with regards
Jonathan Westerholt