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,
Attachment: Output of misc/cron/archive.sh with memory error
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.
hm, I added a comment yesterday, but it seams to be disappeared (The file that I attached at the same time is still there)...
I checked the output of misc/cron/archive.sh (see file) and I get the memory error at this point:
Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 24 bytes) in .../core/DataTable.php on line 952
And I cannot adjust any php settings on my webspace.
Does it get any farther if you create a bootstrap.php file containing:
<a class='mention' href='https://github.com/ini_set'>@ini_set</a>('memory_limit', '256M');
I tried to adjust the memory it with the bootstrap.php but it didnot change anything (neither online nor with the script).
Upgrading to a newer version of php might help (eg memory leak fix for circular references).
Otherwise, I don't have any other suggestions at the moment. Sorry.
Found another comment to this problem: [http://www.heise.de/security/news/foren/S-Re-Piwik-Seiten-mit-hohem-Traffic/forum-170852/msg-17785147/read/]
It says, that for websites with 20000 visitors per day, the archive-script needs more than 1 GB memory (and the server only has 1 GB).