TYPO3 Core

The Log module currently has some performance issues:

• When selecting a larger time frame as a constraint you can easily run into memory problems, leading to a error 500
• Once this happens, you can't access the be module again, because the belog will automatically load the saved constraints, which lead to the memory exhaustion, from the beuser module data.

Some ideas how to fix this:

• Automatically reset the belog constraints, once the php execution runs into an error, so the belog can easily be accessed again.
• Evaluate the belog code for possible memory leaks and other performance bottlenecks.