Comments on: concrete5 and core dump files http://www.smartwebprojects.net/concrete5-blog/161/concrete5-and-core-dump-files/ Tutorials, notes, concrete5 addons and themes bulletin Tue, 06 Jul 2010 23:44:35 -0500 http://wordpress.org/?v=2.8.1 hourly 1 By: admin http://www.smartwebprojects.net/concrete5-blog/161/concrete5-and-core-dump-files/comment-page-1/#comment-283 admin Sun, 27 Sep 2009 22:39:35 +0000 http://www.smartwebprojects.net/concrete5-blog/?p=161#comment-283 Yes, that's really odd. I've done some benchmarking and concrete5 indeed seems to use not much resources. It's a really strange issue and it's hard to investigate it - it happens randomly at different stages (even if you just refresh the page) or doesn't happen at all - sometimes it happens on outputAutoHeaderItems, sometimes on block render, but not always on the same block. And the most strange thing is that script doesn't die or break, it just creates a core dump file, but works a normal way. Yes, that’s really odd.

I’ve done some benchmarking and concrete5 indeed seems to use not much resources. It’s a really strange issue and it’s hard to investigate it – it happens randomly at different stages (even if you just refresh the page) or doesn’t happen at all – sometimes it happens on outputAutoHeaderItems, sometimes on block render, but not always on the same block.

And the most strange thing is that script doesn’t die or break, it just creates a core dump file, but works a normal way.

]]> By: Andrew E. http://www.smartwebprojects.net/concrete5-blog/161/concrete5-and-core-dump-files/comment-page-1/#comment-282 Andrew E. Sun, 27 Sep 2009 22:13:43 +0000 http://www.smartwebprojects.net/concrete5-blog/?p=161#comment-282 Thanks for the write-up. Obviously, this is treating a symptom and not the source of the problem. We try to be resource-conscious, but certain aspects of concrete5 are memory intensive. I haven't seen this error on our particular hosting, or any of the third party hosts we refer people to. It's really odd. Thanks for the write-up. Obviously, this is treating a symptom and not the source of the problem. We try to be resource-conscious, but certain aspects of concrete5 are memory intensive. I haven’t seen this error on our particular hosting, or any of the third party hosts we refer people to. It’s really odd.

]]>