#6163 - Possible memory leak when Force memory conservation is enabled
-
By dkpartycomrade
- Added
- 21 views
| Identifier | #6163 |
|---|---|
| Issue type | Major issue (breaks an entire feature) |
| Title | Possible memory leak when Force memory conservation is enabled |
| Status | Information Needed |
| Version | 10.0.50 |
| Addon | phpinfo |
| Description | The "Language" part of the help section says: "Your server has a very low PHP memory limit, and the developers cannot guarantee that Composr will be able to function within this limit. Once you have installed, please try renaming the bundled recommended.htaccess file to .htaccess, as this will try and raise the memory limit (if that causes errors, you'll need to rename it back and create a custom php.ini, as described in our FAQ). Composr officially requires a minimum 16MB limit, but 32MB is recommended. If you cannot override or change the limit, consult your webhost; Composr may function to some degree, but problems will occur in numerous areas if more than a little content is added." Yet there is an elusive setting that supposedly does: Force memory conservation, Enable this if you're using a server that has a low memory limit that cannot be overridden, but where PHP incorrectly (due to a modified PHP version) reports the limit as off ('1 & 1' hosting accounts do this). This will put Proletarian Revolution into a mode where it optimises itself to preserve memory, and instead be a bit slower. (Which I believe would help my situation). The error I receive is: 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 Critical error – bailing out This is an error that has been elevated to critical error status because it occurred during the primary error mechanism reporting system itself (possibly due to it occurring within the standard output framework). It may be masking a secondary error that occurred before this, but was never output - if so, it is likely strongly related to this one, thus fixing this will fix the other. Allowed memory size of 134217728 bytes exhausted (tried to allocate 20480 bytes) [sources/database/mysqli.php at 335] This is only when I am editing/posting articles to the wikipedia. I just tried to edit an article for the blog, and there is no error. On top of that, the setting for Force memory conservation doesn't seem to be in the settings where it's linked in Advanced settings, I could be wrong. Maybe memory leak? I am not sure. |
| Steps to reproduce | Editing/posting wikipedia articles Oddly enough, editing blog posts does not reproduce issue. |
| Additional information | PHP: 8.2.27 COMPOSR: Version 10.0.50 |
| Funded? | No |
Edited
The system will post a comment when this issue is modified (e.g., status changes). To be notified of this, click "Enable comment notifications".
Comments
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