The problem is the de-registering the core-bundled version of jQuery, and re-registering using your own, arbitrary version. Do not de-register core-bundled versions of scripts (especially jQuery) in order to register arbitrary/custom versions of those scripts. Doing so can and will cause breakage and unintended consequences. If you’re doing so in order to cause your custom … Read more
MO files (the translations) are memory expensive, especially for languages whose characters need multiple bytes for each – like Arabic, Hebrew, Chinese and so on. So an increased memory usage is normal when you are using translated text. But 33 MB is really not that much. I wouldn’t worry about that. More important are sudden … Read more
Try memory_limit = 128M in php.ini. Your syntax may be wrong. You can run a function called phpinfo to see what kind of memory allocation you really have. Make a plain text file and call it phpinfo.php and put just this line in it: <?php phpinfo(); ?> then put the file in the root of … Read more
I’m not sure how you dump all the memory to a file without doing this repeatedly (if anyone knows an automated way to get gdb to do this please let me know), but the following works for any one batch of memory assuming you know the pid: $ cat /proc/[pid]/maps This will be in the … Read more
Regardless of your php settings, there is some script that is wither bad configured and it is eating up more resources that it should. Consider updating your plugins, and see what is happening with the “types” plugin. On your first error ( clicking pages ), the types plugin is where it stops. In the second, … Read more
The “cached” total will also include some other memory allocations, such as any tmpfs filesytems. To see this in effect try: mkdir t mount -t tmpfs none t dd if=/dev/zero of=t/zero.file bs=10240 count=10240 sync; echo 3 > /proc/sys/vm/drop_caches; free -m umount t sync; echo 3 > /proc/sys/vm/drop_caches; free -m and you will see the “cache” … Read more
You could try to tackle this problem in blocks of posts instead of all of them at the same time, you are currently loading all the posts into the memory and then you query the database using these posts which isn’t terribly efficient. You could get the total amount of post, and then query them … Read more
Simplest way to see what is causing it is to disable all plugins and add them back one at a time. If that doesn’t reveal it, switch to a default theme. After that I’d say it is something server side. To answer your question though – caching should help but it depends on what is … Read more
At the top of your wp-config.php you add define(‘WP_MAX_MEMORY_LIMIT’, ‘256M’); this will work only in back-end and do not increase memory in front-end. If this doesn’t work in your site, you can also add this define(‘WP_MEMORY_LIMIT’, ‘256M’);
You are 100% correct. It is not a good practice to free up RAM. This is likely an example of cargo cult system administration.