Skip to main content

This site requires you to update your browser. Your browsing experience maybe affected by not having the most up to date version.

Archive /

Our old forums are still available as a read-only archive.

Moderators: martimiz, Sean, biapar, Willr, Ingo, simon_w

Fatal error on flush


Reply


7 Posts   2339 Views

Avatar
quicked

Community Member, 32 Posts

13 December 2007 at 3:22am

Now every time I flush I get:

Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 6291456 bytes) in C:\WINDOWS\Temp\silverstripe-cacheC--xampp-htdocs-silverstripe\cache.php on line 4

The flush seems to work though

Avatar
Sigurd

Forum Moderator, 628 Posts

17 December 2007 at 11:40am

Looks like the page you're loading is using more memory that you've set; just increase this until a future release with improved memory overhead arrives.

Avatar
haggen

Community Member, 1 Post

19 December 2007 at 1:16pm

I had the same error, then I tried with 48, 90, 120, and 180M of memory limit.. still not workiing!
Is it impossible to use SS 2.2.0 by now ?

Avatar
Sigurd

Forum Moderator, 628 Posts

19 December 2007 at 1:25pm

haagen can you please explain exactly what you were doing, as you've clearly hit a bug there we need to squash.

Avatar
adrianmak

Community Member, 6 Posts

20 December 2007 at 10:23pm

Edited: 20/12/2007 10:24pm

I'm having this problem too when do a flush. Even though I set memory_limit up to 64M in php.ini and restart apache, this problem still exists.

My page is just demo page installed by default. My development platform is on windows using the WAMP all-in-one package.

ps I can't make a flush to reflect my changes in template file.

Avatar
a-tech

Community Member, 39 Posts

18 March 2008 at 6:43pm

Getting same error, I don't really want to set my limt above 64 megs.

It happened after I uploaded a new image for an asset.

Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 68122 bytes) in /home/nate/domains/bassdrop.co.nz/public_html/sapphire/core/Requirements.php on line 159

Any fix for this?

Avatar
a-tech

Community Member, 39 Posts

18 March 2008 at 7:06pm

Okay, so I see its a feature-lock for 2.2.3. Good.

http://open.silverstripe.com/ticket/1929

For now I can increase my mem limit, but as is said in the bug comments, the assets folder only has a moderate number of images and this is only going to increase.

Looking forward to the next release more than ever now!