#6163 - Possible memory leak when Force memory conservation is enabled

This is a spacer post for a website comment topic. The content this topic relates to: #6163 - Possible memory leak when Force memory conservation is enabled
Automated message: This issue was created using the Report Issue Wizard on the Composr homesite.
After a while of going back and forth between looking at the files in FTP and the hosting website, I confirmed that the PHP memory was set, at least on the hosting platform's side at 512 MB or around that. Thus, I then added some blocks of code to the website to determine whether PHP memory was set to, and I got 200 MB. I added another parameter to tell me if it would be able to allocate 200, and it was successful. Yet, I still got issues with editing and adding pages to the Wikipedia, drawing into a memory block at around 120 MB. After a while, I ended up looking in my plugins to remove unnecessary items that could of contributed, and I ended up removing the "weather" plugin that uses Yahoo API, and sure enough, I am able to edit items off the wiki now without a memory problem? I'll add another note if there is any update.
I spoke too soon, the problem remains persistent on editing wiki page titles:

Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 20480 bytes) in /home2/xdsyeite/public_html/sources/database/mysqli.php on line 335

Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 20480 bytes) in /home2/xdsyeite/public_html/sources/global2.php on line 846
Got it. I'll have to look into this later after 11 beta 7 is out and I have a clean working directory.
Thanks Patrick. I confirmed a few things to save you some time.

The hosting platform has set a maximum of 500 MB of PHP memory.
PHP local memory that the website is running off of is set at 128 MB, however the global php settings for the hosting are indeed set to the 500 MB.
I confirmed that the website was able to allocate at least 200 MB, and it would seem that composr generally anyways runs off little ram, as stated 32 mb is recommended.

I ended up going to this file into FTP and looking at the code; sources>global2.php>[line 971] $default_memory_limit = '128M';

I changed this to 400 and still there was no fix. I think somewhere along the wikipedia area is another issue outside of the livechat feature (header problem). I have cycled down the issue to be editing certain pre-existing articles, and it also does not display certain other made articles within the admin zone > wiki pages. So I think there is a memory leak somewhere in the wiki portion, but then again I really am not sure.
To me, it sounds like a memory leak or an infinite loop somewhere.

11 beta7 entered testing stage yesterday so it will only be a few more days before release (hopefully), and then I can switch over to v10 and take a look.
@dkpartycomrade I will need more information.

Can you give me a direct link to a Wiki article which triggers the error when you try to edit it?

System message - Issue updated

The details or status of this tracker issue were updated by PDStig
0 guests and 0 members have recently viewed this.