#6163 - Possible memory leak when Force memory conservation is enabled
0 guests and 0 members have recently viewed this.
The top 3 point earners from 23rd Nov 2025 to 30th Nov 2025.
| PDStig |
|
|
|---|---|---|
| Master Rat |
|
|
| cupper3 |
|
There are no events at this time
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
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.
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.
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