Community Forums › Forums › Archived Forums › General Discussion › Memory leak in Gen or WP?
- This topic has 2 replies, 2 voices, and was last updated 8 years, 2 months ago by dev.
-
AuthorPosts
-
January 31, 2016 at 7:02 pm #178005devParticipant
I'm getting a number of Internal Server Error screens. I know a lot about these and so I'm not asking for help on solving the issue. I'm only asking if there is any remote possibility that there is a memory leak in either the current versions of Gen or WP. I'm using the Dynamik Web Builder and I've asked the same question to them.
I'm telling the client's ISP that it is their issue, but they are pointing to the website's CMS, themes and plugins. I've run without plugins and still get some of these errors... usually in the Admin area of WP... doing something simple like trying to open a page to edit it.
It is very random, and intermittent. I've turned on both PHP and WP error logging, but that has not been any help. The ISP says that their resource monitoring system is killing the PHP process. They say it is larger than 60MB which is their limit. I fail to see how anything in WP could spawn a process that large. or even close to that large.
This has only been happening since the latest version of Gen.
I really, really doubt it is Gen or WP or DWB... but thought I'd ask because in the last 40 years I've been programming I've learned that I don't know everything!
Maybe someone has some ideas I can take to the ISP.
Thanks.
February 1, 2016 at 6:51 am #178041Victor FontModeratorI also doubt there's anything in WP or Gen that would be causing a memory leak, otherwise a lot of sites would be experiencing it. I would look for cron jobs or plugins with long running scripts. The WordPress performance profiler plugin my help, but it may slow down the site while active: https://wordpress.org/plugins/p3-profiler/
Regards,
Victor
https://victorfont.com/
Call us toll free: 844-VIC-FONT (842-3668)
Have you requested your free website audit yet?February 1, 2016 at 12:18 pm #178074devParticipantThanks for the follow-up note. Here is what I heard today from the host-ISP:
===========================
I apologize for the ongoing problems with this. I think we may have just resolved the issue though. There is an automated resource usage monitoring program in place on the shared hosting servers. In part, the system enforces memory usage limitation on processes. By policy, scripts on shared hosting are only allowed 64MB of RAM usage. However, we generally don't enforce that until they are much higher, typically around 256MB in size. When the limit is exceeded, the underlying php5.cgi process itself can be automatically ended. That in turn causes mod_fcgid to not receive proper CGI output back from PHP, which then causes Apache to return the 500 status error.The new web account is running on a newly released FreeBSD 10 operating system build. In doing some testing with the PHP processes for the account, it looks like FreeBSD 10 may be reporting the usage a bit higher due to kernel settings than the prior FreeBSD releases did. Our admins are currently checking into that, but, anecdotally, it appears to be the case. If that is proven to be the case, the resource usage monitoring system will be updated system wide to account for that.
========================I knew it was not on my end!!
Thanks again.
-
AuthorPosts
- The forum ‘General Discussion’ is closed to new topics and replies.