- NewsmagRequirements for Newsmag
Yes. Visual Composer is a memory hog.
Also if your site gets overloaded with requests. I just posted note on the Newsmag forum about our site getting slammed by the YANDEX bot and our server processes when from normal of about “1” up to “49” … which is 50x normal (!)… it’s actually worse than that. We blocked Yandex and it’s coming down to normal.
Hm. Weird. I sit corrected. I wonder if new version has some issue with Nginx …
presumably you already updated your php.ini file to increase memory, upload size and execution time from the often insufficient defaults. That was my issue with VC initially.
Probably best to roll back to prior version of VC and see if that works?
Hi
my solution to this happening sometimes is to first “save” things on right side of the page you’re editing, then go to edit item with pencil, then save that change, then immediately save the main save button. Sometimes to add a new row I need to click add, then save main item, then edit it when it goes into spin of doom.
Seems to be an ajax memory thing. Comes and goes, oddly enough. Even in Chrome, which is usually better about that.
This is usually an issue with php memory limit as of WP 4.0, or if you’re uploading an image with a post page open, WP has annoying habit of doing a draft save while you try to upload and you get http error. Also sometimes going to the media manager there is nothing there. Not theme related as I also have this issue with two other themes (e.g., Woo Canvas), and increasing PHP memory and upload size limit helped “most of the time” — and also doing a draft save manually before uploading an image, if uploading from post.
With media manager, also sometimes no matter what seems like I have to “drag” image second time. Annoying. This all started with WP 4.0 in our case.
Thanks for the quick response. It’s odd because I migrated from your Newspaper theme and if memory serves correctly, I believe it added proper spacing between paragraphs in the comment section. When using the default wordpress theme, it seems to add a line (space) between paragraphs in the comments box. I was thinking this might have something to do with the stylesheet but perhaps not.
Hi Chris,
Thanks a lot for the information, it sure was the issue with memory allocation, and bunch of other stuff on the php.ini that had to adjusted. Demo version looks great on the local environment.
Regards,
-Asim
Usually it’s a memory allocation issue with PHP, such as too short process time, or too small memory allocation (e.g., 32MB vs 256MB); and/or the maximum “upload” size is too small. Checking your php.ini setup file usually solves that.
Yeah. I have that issue notably with Internet Explorer; less so with Chrome on Windows 7/64.
The trick I’ve found with that is to do ‘save’ on right side to update, then try again, and if it spins, hit save. Then if it shows up, then go to edit.
Stupid I know. Went through this same issue over the weekend with migrating site to Newsmag from Woo Canvas. Basically it’s the Visual Composer uses a bit of memory, and since it’s all ajax based and uses WP “transient” settings, seems like browser runs out of something.
And I’m on a Mac Pro with 32GB of RAM, running Windows in 64 bit – what memory am I running out of ? 🙂
So try this:
1) clear your browser temp files/cache.
2) try the “save” button right side before doing ANYTHING.
3) if it spins and spins, try save changes; then if it drops into the slot in the preview, then click the pencil icon to EDIT it once it’s there.
Stupid, I know … but that’s how I got it done! 🙂
Often this is from either
a) not enough memory allocated to PHP for your domain; which I recommend 256MB or higher. Some hosts default that to as little as 16MB.
b) sometimes as of WP 4.0, the WP system cannot affix an image while it’s doing a soft backup of the story (a draft backup); often you can do “save draft” then add the image.
c) check you can actually just upload things to the media manager at all, separate from placing them in to a post while live editing.
Hi,
Please try to increase the memory allocated to php: http://codex.wordpress.org/Editing_wp-config.php#Increasing_memory_allocated_to_PHP try to increase to 96M.
Thanks!
Now I can’t even disable plugins to log into Admin – i am getting these errors
/home3/redcarp8/public_html/error_log:
[04-Mar-2015 02:29:59 UTC] PHP Fatal error: require_once(): Failed opening required ‘/home3/redcarp8/public_html/wp-content/plugins/js_composer/include/classes/shortcodes/shortcodes.php’ (include_path=’.:/usr/php/54/usr/lib64:/usr/php/54/usr/share/pear’) in /home3/redcarp8/public_html/wp-content/plugins/js_composer/include/classes/core/class-vc-base.php on line 243
[04-Mar-2015 02:30:44 UTC] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 32 bytes) in /home3/redcarp8/public_html/wp-content/themes/Newsmag/includes/wp_booster/td_block.php on line 63
[04-Mar-2015 02:31:06 UTC] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 72 bytes) in /home3/redcarp8/public_html/wp-includes/taxonomy.php on line 2156
[04-Mar-2015 02:31:20 UTC] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 72 bytes) in /home3/redcarp8/public_html/wp-content/themes/Newsmag/includes/wp_booster/td_block.php on line 64
[04-Mar-2015 02:31:26 UTC] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 32 bytes) in /home3/redcarp8/public_html/wp-content/themes/Newsmag/includes/wp_booster/td_block.php on line 62
[04-Mar-2015 02:31:38 UTC] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 32 bytes) in /home3/redcarp8/public_html/wp-includes/wp-db.php on line 1981
[04-Mar-2015 02:31:43 UTC] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 72 bytes) in /home3/redcarp8/public_html/wp-includes/taxonomy.php on line 2664
[04-Mar-2015 02:31:53 UTC] PHP Warning: require_once(/home3/redcarp8/public_html/wp-content/plugins/js_composer/include/classes/shortcodes/shortcodes.php): failed to open stream: No such file or directory in /home3/redcarp8/public_html/wp-content/plugins/js_composer/include/classes/core/class-vc-base.php on line 243
[04-Mar-2015 02:31:53 UTC] PHP Fatal error: require_once(): Failed opening required ‘/home3/redcarp8/public_html/wp-content/plugins/js_composer/include/classes/shortcodes/shortcodes.php’ (include_path=’.:/usr/php/54/usr/lib64:/usr/php/54/usr/share/pear’) in /home3/redcarp8/public_html/wp-content/plugins/js_composer/include/classes/core/class-vc-base.php on line 243
[04-Mar-2015 02:38:57 UTC] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 72 bytes) in /home3/redcarp8/public_html/wp-content/themes/Newsmag/includes/wp_booster/td_block.php on line 64
[04-Mar-2015 02:39:03 UTC] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 72 bytes) in /home3/redcarp8/public_html/wp-includes/taxonomy.php on line 2662
[04-Mar-2015 02:39:10 UTC] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 72 bytes) in /home3/redcarp8/public_html/wp-content/themes/Newsmag/includes/wp_booster/td_block.php on line 62
[04-Mar-2015 02:39:20 UTC] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 72 bytes) in /home3/redcarp8/public_html/wp-content/themes/Newsmag/includes/wp_booster/td_block.php on line 63
[04-Mar-2015 02:39:21 UTC] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 32 bytes) in /home3/redcarp8/public_html/wp-content/themes/Newsmag/includes/wp_booster/td_block.php on line 63
[04-Mar-2015 02:39:24 UTC] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 32 bytes) in /home3/redcarp8/public_html/wp-includes/taxonomy.php on line 2157
[04-Mar-2015 02:39:31 UTC] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 72 bytes) in /home3/redcarp8/public_html/wp-content/themes/Newsmag/includes/wp_booster/td_block.php on line 63
[04-Mar-2015 02:39:31 UTC] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 72 bytes) in /home3/redcarp8/public_html/wp-includes/taxonomy.php on line 2107
[04-Mar-2015 02:39:38 UTC] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 64 bytes) in /home3/redcarp8/public_html/wp-content/themes/Newsmag/includes/wp_booster/td_block.php on line 63
[04-Mar-2015 02:39:39 UTC] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 64 bytes) in /home3/redcarp8/public_html/wp-includes/wp-db.php on line 1981
[04-Mar-2015 02:40:00 UTC] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 12288 bytes) in /home3/redcarp8/public_html/wp-content/themes/Newsmag/includes/block_templates/td_block_template_1.php on line 77
[04-Mar-2015 02:40:21 UTC] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 72 bytes) in /home3/redcarp8/public_html/wp-includes/wp-db.php on line 1975
[04-Mar-2015 02:40:26 UTC] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 64 bytes) in /home3/redcarp8/public_html/wp-content/themes/Newsmag/includes/wp_booster/td_block.php on line 63
[04-Mar-2015 02:40:28 UTC] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 114 bytes) in /home3/redcarp8/public_html/wp-includes/plugin.php on line 108
[04-Mar-2015 02:40:38 UTC] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 72 bytes) in /home3/redcarp8/public_html/wp-content/themes/Newsmag/includes/wp_booster/td_block.php on line 63
[04-Mar-2015 02:40:44 UTC] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 72 bytes) in /home3/redcarp8/public_html/wp-includes/taxonomy.php on line 2156
[04-Mar-2015 02:49:18 UTC] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 8388608 bytes) in /home3/redcarp8/public_html/wp-content/plugins/wordfence/lib/wfBrowscap.php on line 87
[04-Mar-2015 02:49:34 UTC] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 8388608 bytes) in /home3/redcarp8/public_html/wp-content/plugins/wordfence/lib/wfBrowscap.php on line 87
[04-Mar-2015 02:49:48 UTC] PHP Fatal error: require(): Failed opening required ‘wfBrowscapCache.php’ (include_path=’.:/usr/php/54/usr/lib64:/usr/php/54/usr/share/pear’) in /home3/redcarp8/public_html/wp-content/plugins/wordfence/lib/wfBrowscap.php on line 87
[04-Mar-2015 10:00:51 UTC] WordPress database error You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ” at line 1 for query SELECT * FROM wp_fsg_galleries WHERE fsg_id= made by require(‘wp-blog-header.php’), require_once(‘wp-includes/template-loader.php’), include(‘/themes/Newsmag/single.php’), td_api_single_template::_helper_show_single_template, load_template, require_once(‘/themes/Newsmag/single_template_3.php’), locate_template, load_template, require_once(‘/themes/Newsmag/loop-single-3.php’), td_module_single_base->get_content, apply_filters(‘the_content’), call_user_func_array, do_shortcode, preg_replace_callback, do_shortcode_tag, call_user_func, fsg_shortcode_renderer, make_gallery_html
[04-Mar-2015 15:21:02 UTC] WordPress database error You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ” at line 1 for query SELECT * FROM wp_fsg_galleries WHERE fsg_id= made by require(‘wp-blog-header.php’), require_once(‘wp-includes/template-loader.php’), include(‘/themes/Newsmag/single.php’), td_api_single_template::_helper_show_single_template, load_template, require_once(‘/themes/Newsmag/single_template_3.php’), locate_template, load_template, require_once(‘/themes/Newsmag/loop-single-3.php’), td_module_single_base->get_content, apply_filters(‘the_content’), call_user_func_array, do_shortcode, preg_replace_callback, do_shortcode_tag, call_user_func, fsg_shortcode_renderer, make_gallery_html
One solution is to use a “lazy load” function, however this runs risk of some items not loading at all, if browser memory/cache times out.
What really sped up our use of such was using mod_pagespeed … this optimizes images including conversion to webp for Chrome, etc., caches with opcache if setup properly, etc.
And of course make sure the thumbs are highly compressed (like using the “50” setting in your functions.php vs default 90, etc.).
Better optimized images to start with helps also;
this image is 41kb and could be nearly half that, especially since B/W/greyscale:
http://dev.promicabana.de/wp-content/uploads/Justin-Bieber-21-Geburtstag-6-559x420.jpg
I’m sure you know all that … just chiming in as I tend to do. 🙂
After updating theme to version 4.6.2 from 4.6.1 and try to update new visual compozer my homepage shows this :
Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 71 bytes) in /home/kanal9tv/public_html/wp-includes/plugin.php on line 207
Yes, so you should probably go google how to manage yoru Windows Azure Cloud account — YOU are the one, bro, who mentioned that. Not sure what your azure cloud has to do with anything if that isn’t your server platform.
If running Linux – why not look at the link I provided on how to setup opcache on Ubuntu on Linux????????????????????????????????????????????????????????
AGAIN:
http://www.davidado.com/2014/09/26/how-to-set-up-nginx-with-php-5-5-and-php-fpm-on-ubuntu-14-04/
FROM THE ABOVE PAGE………..
this might not work for you, but why not try it – or contact your hosting support, or RTFM for the platform you’re using???????????????
E.g.,
# Opcache
opcache.enable=1
opcache.enable_cli=0
opcache.memory_consumption=128
opcache.interned_strings_buffer=16
opcache.max_accelerated_files=6000
opcache.max_wasted_percentage=5
opcache.use_cwd=1
opcache.validate_timestamps=1
opcache.revalidate_freq=60
opcache.revalidate_path=0
opcache.save_comments=1
opcache.load_comments=1
opcache.fast_shutdown=1
Okay – sorry — you should wait for somebody else to help as you don’t seem to know how to google stuff for support which is entirely NOT theme related.
Apologies – I will stop trying to help you on stuff.
So i need to increase my php memory limit? i increase post max size and upload max size anything else to do in php.ini?
Might be not enough memory for visual composer? Allocate 512MB for php for the domain.
You likely already did that.
Hopefully somebody else running theme on NGINX will chime in!
Hi,
@Christopher Thank you for your suggestion. We will try to add a message more visible, but generally most people don’t read this kind of messages.
@vrtech We still test the latest version of Visual Composer as we try to solve the memory issue. Also note that Visual Composer will be updated only on Newspaper 5. Please send an email at contact@tagdiv.com provide more details about your issue and we will try to provide a solution.
@momma You don’t have to buy it or register it, the Visual Composer plugin that comes with the theme is licensed to the theme. Please ignore the plugin update message, we will include it in the next theme update.
Thanks!
Sorry. I am using the Newsmag theme which has this option. The Newspaper theme does not yet have it, but is supposed to get new version once the memory hog issue is sorted which is causing sites to die with latest version of VC.
I am using Newspaper theme on couple of other things, but using the built in post grids including with the theme. 🙂
-
This reply was modified 11 years by
simchris.
Hi,
What version of Visual Composer do you use? There are some memory issues with the latest version, try to install version 4.3.5, then optimize the site – https://forum.tagdiv.com/how-to-make-the-site-faster/ (especially the gzip compression, images, cache and browser leverage).
Reduce the number of ajax using elements on page (mega menus, ajax pagination/load more/infinite load). Also reduce the number of blocks on your main page.
If nothing works please send an email at contact@tagdiv.com and provide more details.
Thank you, Emil G.
-
This reply was modified 11 years by
Emil G.
The current version of Visual Composer is a memory hog. Not directly related to theme.
Hopefully next version will be better.
Ironic how so many people were whining about not getting the latest version of VC the moment it was released, and now they have it, it’s not that great.
My site has 95 speed rating without modifying the speed booster file, using all my recommendations.
Render blocking css/js are not a deal breaker for the web. If you can fix everything else you’re good.
Of course, I’m spoiled with 12core XEON and 32GB RAM.
Sorry to be captain obvious here, but if he is able to use everything properly on another domain on the same machine – as he says – then VC isn’t the problem. Nor is the memory limit.

@Orlando I’d suggest making sure you have the latest version of WordPress, and then I’d FTP a fresh copy of WordPress over your existing copy to remove any issues within the files. Whatever the problem is, it’s not Newsmag or Visual Composer causing the issue. Shouldn’t be server config either.
Hi,
We’re looking into this, on our side it uses a small amount of memory, just a few MB from the older version, on some clients it uses around 80 MB more than the previous version. We’re trying to replicate this issue on our side and identify the cause.
Thank you, Emil G.
Apparently the current version of Visual Composer is a memory pig …. might not be compatible with your server due to some bug in that. Dunno.
Hi Chis,
I explained that I do not use a hosting but a server
PHP version 5.4
memory_limit set to 1024M
but also by changing the parameter to 4096M
remains the problem.
Ask your hosting provider fir support on your histing account, to learn how to set memory limit for php… Usually set via hosting panel or php.ini file. Google how to increase memory limit for php.