I told you before that this blog has problem in redirecting users who posted comments at this blog into the right page where they posted their comments. My previous post about this is “Wordpress Redirect After Commenting, Failed.”
Although I’m already at my limit, but I never give up (that’s my way of blogger lol). I checked my site and found files at the root directory of my site with the filenames begin with the term “core”. Take a look at the screenshot below:
And these core files are eating too much space in my hosting account.
Through searching I found out that this files are called “core dumps”. They are called like this because this files are logs of core memory error. The Wikipedia has this idea:
A core dump is the recorded state of the working memory of a computer program at a specific time, generally when the program has terminated abnormally (crashed).[1] In practice, other key pieces of program state are usually dumped at the same time, including the processor registers, which may include the program counter and stack pointer, memory management information, and other processor and operating system flags and information. The name comes from the once-standard memory technology core memory. Core dumps are often used to diagnose or debug errors in computer programs.
On many operating systems, a fatal error in a program automatically triggers a core dump, and by extension the phrase “to dump core” has come to mean, in many cases, any fatal error, regardless of whether a record of the program memory is created.
The term is used in jargon to indicate any circumstance where large amounts of unedited data are deposited for further examination.
With this information, I am now suspecting that the wordpress system installed in my hosting account particularly the one used by this blog has problem in which some scripts are terminated by the server to avoid server crash.
So, I checked the error log of my hosting account and found out that the wp-comment-post.php file which is one of the Wordpress files are always terminated and the error says “Premature end of script header”.
This error message, “Premature end of script header”, is not really clear and is not even giving me hint of what particular line in the script is having error. But I am thinking that the error is on the redirect code just like what I mentioned before on my previous post. The code is:
wp_redirect($location);
I think, the value of the variable “$location” is wrong. That’s why when the “wp_redirect” function is executed, the system goes wrong.
Now, if it is really the problem, then the code that enters the value of the variable “$location” has having problem in getting data. This code is:
$location = ( empty($_POST[’redirect_to’]) ? get_permalink($comment_post_ID) : $_POST[’redirect_to’] ) . ‘#comment-’ . $comment_id;
$location = apply_filters(’comment_post_redirect’, $location, $comment);
Analyzing further really makes me feel headache.
I asked help from my host but seems the technical support is busy that they couldn’t give me even a few minutes just to give me hint on what to do.
If ever you have knowledge on this kind of problem, please advise me what to do.
By the way, thanks to the PinoyBlogero. He suggested that the problem might be in redirect conflict. I am still checking this possibility.
| 2.8 |

SELaplana, 28 January 2008 at 




January 28th, 2008 at 3:00 pm
I’ve had this problem with several of my blogs before. You are right that the server is terminating a script which is causing a lot of cpu load or high memory usage.
Server environments have some restrictions on PHP script with how much memory they can use in one instance or long long they are allowed to run. From experience, memory allotment is set between 8MB to 36MB per script with execution time ranging between 10 secs to 60 seconds. If any script exceeds this limit, they are prematurely terminated. That sometimes results in core dumps.
I’ve actually recently blogged about why WP Plugins Should Be Regulated. It is possible that for every comment submitted by a visitors, additional executions are being made by WP which exceeds the server limitations. INcreasing these limits will not solve the problem since more WP plugins will just gobble them all later on.
January 28th, 2008 at 3:04 pm
Sonnie had a similar problem where a plugin was injecting additional rows of data in the wp_options table. It grew to about 27MB. That means for every page load (all WP page load accesses wp_options), the blog eats up at least 27MB of memory. Multiply that with any number of concurrent visitors and you get the picture.
January 28th, 2008 at 4:30 pm
Hi! Thank you so much for the input. I read also your post. I’m sorry I missed that post. I should’ve read that post earlier.
I understand a little now about my problem. And I am still thinking what to do to fix the problem of this blog.
I am now asking God to make this idiot minds became genius…
January 28th, 2008 at 4:37 pm
I just wish I can fix this before the february ends
January 28th, 2008 at 6:59 pm
offtopic: i just like to congratulate you for being Kontera’s Publisher of the Month! Ang galing!
January 28th, 2008 at 9:31 pm
My theory is that your WP plugin is overloading the memory limit. I suggest is to upgrade it to the latest version or disabling it to see if the core files stop popping up.
January 28th, 2008 at 9:38 pm
Marhgil >>> thanks a lot.
Yuga >> thanks for the suggestion. I will try it now.
January 29th, 2008 at 1:55 am
offtopic: oo nga astig nasali ka dun! hehehe,.. congrats din!
January 29th, 2008 at 1:29 pm
makikibati din.. congrats! Kontera’s Publisher of the Month
February 11th, 2008 at 1:11 pm
[...] am still looking for the real cause of this error. I also mentioned it already on my post “Wordpress Problem at this Blog.” Automatically receive updates via email. Enter your email address to [...]