Support community for TTG plugins and products.
NOTICE
The Turning Gate's Community has moved to a new home, at https://discourse.theturninggate.net.
This forum is now closed, and exists here as a read-only archive.
You are not logged in.
Pages: 1
Any idea what this means
Unexpected error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 140735015874160 bytes) in SimpleHTMLTag.php on line 113
Offline
Looks like an error message from your server, which obviously failed to fulfill an insane request to allocate 140,000 gigabytes. That's far more than all of the storage I have, including all my raw photos and a years worth of daily backups.
To help you, we'd need to know how you encountered this insanity. We don't even know this was in Backlight. Where did you find this error message? Are you using WordPress for your pages? Any custom code? Any Plugins? Are you using PHPPlugins? What's the URL? How did you trigger this?
--Jim
Offline
And also what version of Backlight 2 are you using?
Rod
Just a user with way too much time on his hands.
www.rodbarbee.com
ttg-tips.com, Backlight 2/3 test site
Offline
Looks like an error message from your server, which obviously failed to fulfill an insane request to allocate 140,000 gigabytes.
It’s not that bad. It’s actually only 128MB. Still far more that should be used on an admin page request.
Offline
Steve, can you provide a link and admin credentials where I can see this error?
Offline
Sorry, it is my local copy. I have two other sites locally that updated to 2.014 no problem. But when I went to this site I received this message. I have updated my hosted sites no problem it is just this one local site that is doing this. Worked fine when i went to the site some weeks ago (as admin that is)
I always work on my site locally then only upload when I have tested it fully, it is the way I have worked since first using TTG some years ago.
Offline
I am sure I have seen this before, but my usual methods of fixing issues, clear template cache, delete sessions and log files and finally making sure permissions are ok have not worked
Offline
appears to be a mac issue. Although I had rebooted my machine and then my other local sites displayed the same problem a second reboot removed the issue on all local sites
Offline
Hi Steve, has the problem stopped happening for you?
Offline
yes, obviously something got stuck in the mac and needed a couple of reboots to clear it.
Offline
Pages: 1