Bug #17774
closed
cli_dispatch.phpsh lowlevel_refindex -c runs into memeory size exhausted
Added by Dirk Diebel about 17 years ago.
Updated about 6 years ago.
Description
i'm trying to run ./cli_dispatch.phpsh lowlevel_refindex -c from shell, but i all i got is this message:
***********************************
Reference Index being TESTED (nothing written, use "-e" to update)
***********************************
PHP Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 40 bytes) in /opt/wwwroot/typo3_src/t3src412/t3lib/class.t3lib_div.php on line 2178
(issue imported from #M6691)
Files
Did you try running the script with full path? Running the script local is not supported by CLI.
Wrong:
./cli_dispatch.phpsh lowlevel_refindex -c
Right:
/path/to/your/typo3/cli_dispatch.phpsh lowlevel_refindex -c
Additionally you can try using another php to compile this script.
Example:
/usr/bin/php5 /path/to/your/typo3/cli_dispatch.phpsh lowlevel_refindex -c
- Target version deleted (
0)
IMHO, issue should be closed.
This is an expected behavior when content grows - adjust max memory size!
Fatal errors are never expected behaviors. And maybe something is wrong, can be fixed or a warning can be given out.
Thats why I will let it stay open.
This Patch fix the Problem under Typo3 6.
I don't test it under Typo3 4
Check this for Typo3 4 and give Feedback
I have some big databases where even memory_limit=1024M is not enough. So this should be fixed. The error occurs too when updating the index (-e).
I tried the patch for TYPO3 4.5 and it did not help (maybe there is less memory used but its not enough).
From the programming logic it really seems to be a bug that the class creates a new instance of itself for each record instead of calling the method in its own instance (but since it is using properties to keep track ($this->word_strings etc) maybe this is necessary (and thus the patch is not good).
- Status changed from New to Needs Feedback
- Is Regression set to No
@Stephan:
Will this be tackled by your current efforts?
If so, give me a ping so I can close the issue
I'm using TYPO3 6.2.11 and still have the memory issue.
The main reason in my eyes is that all rows of a table are fetched at once (exec_SELECTgetRows
) and then analysed, instead of only fetching one row after another.
Also, table sys_log
is analyzed, which is huge in older instances -> see #66338.
- Status changed from Needs Feedback to Under Review
Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/38573
Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/38573
Patch set 3 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/38573
Patch set 4 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/38573
Patch set 1 for branch TYPO3_6-2 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/38587
- Status changed from Under Review to Resolved
- Status changed from Resolved to Closed
Also available in: Atom
PDF