Forums | Mahara Community
Support
/
export all my data (html): failed
04 April 2012, 6:23
hello everybody,
we have problems with the export-function (html)
some user, who have lots of contacts and views can't export all of her data, the apache-errorlog posted:
PHP Fatal error: Out of memory (allocated 31981568) (tried to allocate 40 bytes) in [...] /lib/htmlpurifier/HTMLPurifier/DefinitionCache/Serializer.php on line 33
but they can export the all of views ("some of views")
the problem doesn't depends on the datavolume, users with more data could export without any problems.
has anyone an idea?
greetings
michaela
infos:
- mahara: 1.4.1
- php: 5.3.10
- apache: 2.2.16-6
- mahara default quota per user: 50M
php.ini:
- post_max_size = 48M
- upload_max_filesize = 24M
- memory_limit = 256M
04 April 2012, 16:56
Hi Michaela, the amount of memory needed is probably related to the number of views, artefacts, files, etc., owned by the user, rather than the size of the files. For the moment there's not much you can do apart from raising the memory limit, or asking the user to export only a subset of their views.
In the longer term we'd need to rewrite the html export to use less memory, or at the very least, we could put some limit on the number of artefacts that can be exported and output an error message to the user before the export starts.
18 April 2012, 4:44
We've just run into the same problem on 1.4.2 exporting collections
Have upped our values to
- post_max_size = 256M
- upload_max_filesize = 50M
- memory_limit = 392M
This solved the problem - the portfolios were not big (30-40Mb) when zipped, but contained lots of artefacts and blocks.
Lets hope the server doesn't run out of memory!
18 April 2012, 14:47
Hello Roger,
Thanks for posting the settings you are now using for your server. That might help others who are playing with these numbers as well.
Cheers
Kristina
19 April 2012, 4:00
Hi,
Yes, all seems fine now - its just the export process seems to temporarily needs a large amount of memory for a very short time.
Thanks for replying to Sam and pointing us in the right direction
Roger
19 April 2012, 10:03
helo roger,
sorry, i've commited the changes to my php.ini, but the error still exists.
nevertheless thank you for your advice!
michaela