Does anybody notice the rising CPU usage of your browser when you are at the create post page (Tiny MCE) of your self hosted WordPress blog? Previously when I was using Firefox the CPU usage rose to 50 percent and FF was running fast like a snail. I thought it was because of problems with FF. Last day when I was using Opera Process Explroer was open. I couldn’t believe that Opera too used very much CPU resources. It was then that I realised the culprit was the WordPress Create Post page (A intersection B, lol).
I was amazed when a Google search provided me only one relevent result. The problem is actually with the WordPress “autosave” feature. If autosave is enabled, then the “Save” “Publish” buttons on my post page used to blink. Everything will come to normal once you “Disable AutoSave” on your blog.
To disble AutoSave you need to comment out the function wp_enqueue_script(‘autosave’); from the following file by adding “//” before them. Comment the line in the following files – /wp-admin/post.php /wp-admin/page.php /wp-admin/post-new.php /wp-admin/page-new.php
After commenting the lines should look like – //wp_enqueue_script(‘autosave’);
Upload these files back and you will have solved the problem. Remember that since SutoSave is disabled you must manually save changes while writing a post.
I didn’t notice the CPU usage while using Opera because Opera is better than Firefox at managing memory and CPU. Also the overall perfomance of the Opera was not affected by the presence of the post page. But in FireFox when the page ws open I couldn’t scroll through any of the pages or couldn’t switch tabs by cliking on them.
I found all these information from Richard Timothy’s blog. Thanks Thimothy 
.
Some related articles you may like :
- WordPress blog painfully slow except for front page
- Why is my template selection page in WordPress showing cryptic CSS
- WordPress 2.5.1 update released
- What to do if your firefox wont load a wordpress blog
- How to secure your WordPress installation against hackers
- How to get your new blog post indexed instantly by Google
- My first guest post – at samanathon.com
- Opera doesn’t accept text in Tiny MCE – WordPress
4 Comments
I did a complete upgrade from WP 2.5 to 2.5.1 with a full file update via FileZilla FTP. But I still had the problem. I didn’t exclude any file from the upgrade.
The problem with the Save and Publish buttons blinking is caused by an incomplete upgrade from WordPress 2.5 to WordPress 2.5.1. You don’t have to disable autosave to fix it, you simply have to finish the upgrade. In particular, failing to update the wp-settings.php file causes that specific problem.
Hi Otto could you be a little more specific.. I mean what have to be done after commenting instead of what I said..
A better fix: Reupload all the WordPress files, paying special attention to the wp-settings.php file.
If you don’t upload ALL THE FILES, you will get unpredictable results. This is one of those results.
This is, in fact, reproducible. Install WordPress 2.5.1. Then overwrite wp-settings.php with the old one from WordPress 2.5. Voila.
One Trackback
[...] hunting around with Google and trying many different search strings, I found an answer here. Ajith mentions on his blog that the autosave function on the write post and page pages causes [...]