You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
BugFor errors / faults / flaws / inconsistencies etc.duplicateFor issues that already existed in our issue tracker and were reported previously.MajorIndicates the severity or impact or benefit of an issue is much higher than normal but not critical.
In #766, archiving is browser-triggered. Cron-based archiving can be a workaround to this memory leak because in many configurations, php-cli runs with no memory limit.
In the meantime, try increasing the memory_limit in php.ini.
BugFor errors / faults / flaws / inconsistencies etc.duplicateFor issues that already existed in our issue tracker and were reported previously.MajorIndicates the severity or impact or benefit of an issue is much higher than normal but not critical.
I get the error if I switch to the year view of the current year:
Fatal error: Allowed memory size of 50331648 bytes exhausted (tried to allocate 86 bytes) in ../core/DataTable.php on line 952
I use the auto-archiving via crontab every night.
#766 seams to be a different issue (without auto-archiving).
I have Piwik 0.4.3 installed.
Keywords: memory, archiving,
The text was updated successfully, but these errors were encountered: