By Bruno on Wednesday, 14 January 2015
Replies 9
Likes 0
Views 1.2K
Votes 0
Hello,

I am trying to install v1.3.15 on my local testbed and receive the following error: Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 25236 bytes) in /opt/lampp/htdocs/wanagado/libraries/joomla/table/nested.php on line 1346
Above mentioned figures seem indeed exagerated.
Any idea?
Thanks.
Hi Bruno,

You are hitting this error most likely because coincidentally, the memory_limit has been reached. Can you try requesting your hosting provider to increase the memory_limit in the php.ini ?

Please advise.
Thanks.
·
Wednesday, 14 January 2015 01:12
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi Yasser,
Well I am currently at 128Mb; is it not enouh?
Thanks.
·
Wednesday, 14 January 2015 01:53
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello Bruno,

Yes, based on the error message already mentioned allowed memory 134217728 bytes , perhaps can you try set to 256M and see how it goes?
·
Wednesday, 14 January 2015 01:59
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi Alex,

That would be fine locally but what about shared hosts that usually provide 64M?
It's a bit weired that all of a sudden ES Installer needs so much more memory, is it not?

Thanks.
·
Wednesday, 14 January 2015 02:32
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi Bruno,

I am sorry for the late reply.
I believe this is not so weird if your site having a lot of images. This memory_limit is mostly used for image manipulation. Can you try requesting your hosting provider to increase the memory_limit to 256M and see how it goes.
However, if this issue is not resolved, perhaps you can kindly provide us with backend access and FTP access so that we can inspect and debug the issue on your site.

Please advise.
Thanks.
·
Wednesday, 14 January 2015 11:32
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello,
Having tried on a clean test site, the problem does not occur, even with less memory; apparently the nested.php file involved in the problem causes some loop that exhausts the memory, whatever the size. I am however not sure why it happened on my site and not on a clean install.
Thanks.
·
Wednesday, 14 January 2015 17:47
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi Bruno,

I am really sorry. I can't replicate this issue with our site. Perhaps you can provide us with backend access and FTP access to your site so that we can assist you further on this issue. It is hard for us to guess what's wrong with your site.

Please advise.
Thanks.
·
Wednesday, 14 January 2015 18:12
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi Yasser,

It appears I may have had a corrupt database on my localhost, with newly created fields receiving an ID=0; that might have caused the launcher to be looping.
I'll have to do some home work.

Thanks for your help anyway.
·
Wednesday, 14 January 2015 19:54
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi,

Glad to hear you have found the issue. Please do update us back on this issue whether you have successfully installed EasySocial on your site or not.

Looking forward to hear from you again.
·
Wednesday, 14 January 2015 23:47
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post