Running Out Of Memopry
Fatal error: Allowed memory size of 25165824 bytes exhausted (tried to allocate 88 bytes) in /hsphere/local/home/c75816/gotv4u.com/concrete/libraries/3rdparty/Zend/Cache/Core.php on line 312
In your php.ini on the server there is a line stating the memory_limit with a certain amount of M behind it.
Set that to 64M or 128M (or even more) to solve your problem.
Depending on your host it might be that you can set the limit in your .htaccess by using the following:
php_admin_value memory_limit 64M
CEO - concrete5.org
So I'd suggest that your PHP memory limit is still stuck at that limit, even though you've tried to set it to 256. Some hosts don't allow you to override that value or at least you have to ask them to change it. I'd confirm your memory limit with a phpinfo file.
I've personally never seen PHP throw a fatal error about running out of memory that wasn't caused by not having enough memory. There's a chance that the caching in concrete5 is using too much memory, but again your error message is saying 24MB.
Show us a screenshot of your php info file with the memory limit.
PHP is only going to output that kind of fatal error if PHP has, in fact, run out of memory. Those error messages also report the memory you had available, in your case 24M (1024 * 1024 * 24). Therefore, from the error message itself you can tell that PHP thinks its memory_limit is 24MB and it's stopping at that value.
That's why I said to take a screenshot of your phpinfo, showing what PHP is reporting. Perhaps you've set a higher memory limit, but it's not actually taking effect. Some hosts allow you to override the setting, some don't.
As a quick experiment, I turned the cache on for a site and started to wind back my memory limit. At 32M, no probs at all. At 24M, I still didn't have a problem (but my test site is effectively empty). At 18M, concrete5 would fatal error because of memory, with the same error message as yours, see attached screenshot. If I then repeated this, but with caching off, the site would still work at 18M, but that's because I'm skirting around the lower limits of what the site needs, and caching obviously has memory overhead. This behaviour is all expected.
So what I'm politely suggesting here is that I think you're jumping to the wrong conclusion that concrete5 has a caching bug that is causing your error.