#506 - No way to override inbuilt memory limit
| Identifier | #506 |
|---|---|
| Issue type | Minor issue (breaks specific functionality) |
| Title | No way to override inbuilt memory limit |
| Status | Completed |
| Handling member | Chris Graham |
| Version | 8.1 |
| Addon | General / Uncategorised |
| Description | Composr impsoes a 64MB memory limit, and only raises it in a very small number of hard-coded situations. If you really want to display huge numbers of results on a screen this poses a problem.
Add new hidden value that can be set in Commandr using: [code] :set_value('memory_limit','256M'); [/code] for example. And document in Code Book: " memory_limit - set this to a memory limit to override Composr's built in one (e.g. "128M"). This will make memory bugs on your server more dangerous, so use at your own risk (a memory usage problem can take down a whole server) - although memory bugs are unlikely given that Composr users report if they ever see this error." |
| Steps to reproduce | |
| Funded? | No |
| Hotfixes | hotfix-506, 2012-05-26 7pm.tar Only apply these hotfixes if you absolutely need them and cannot wait until the next release of Composr (releases are more reliable and strictly tested). We provide no guarantee that hotfixes will work; they may even break your site especially if a hotfix depends on another hotfix. Always make a site backup if you attempt to apply a hotfix. As of Composr version 11, the recommended way to apply a hotfix is by following the same steps as an upgrade:
For Composr version 10, manually extract the files (e.g., using 7-Zip) and overwrite files in your Composr installation that are older than the ones in the hotfix (check the file modification date/time). Skip hotfix files that do not exist in your installation. |
| Commits |
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
There have been no comments yet