Bug #64916
closedAvoid serialization of some members of ContentObjectRenderer
100%
Description
UserInternalContentObject is trying to serialize ContentObjectRenderer.
This leads to severe issues also uses lots of memory.
If you set up a page like this
page = PAGE page.10 < styles.content.get page.20 < plugin.tx_felogin_pi1
Install sysext:felogin and add static templates for CSC and felogin!
Add a "text w/image" CE to the page and add at least one image.
you'll get an Exception in FE: Serialization of closure not possible.
(In order to see the Exception you need to set the application context to Development and select the Development-preset in Install Tool.)
The reason is that if the Core is not installed via composer, a closure is registered in the SignalSlotDispatcher.
For some reason, when serializing ContentObjectRenderer, also SignalSlotDispatcher is serialized, which leads to this exception.
The solution is to remove the "hard-wires" between ContentObjectRenderer and TSFE and File(Reference).
Updated by Gerrit Code Review over 9 years ago
- Status changed from Accepted 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/36723
Updated by Gerrit Code Review over 9 years ago
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/36723
Updated by Gerrit Code Review over 9 years ago
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/36723
Updated by Gerrit Code Review over 9 years ago
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/36723
Updated by Markus Klein over 9 years ago
- Subject changed from Avoid serialization of TSFE with ContentObjectRenderer to Avoid serialization of some members of ContentObjectRenderer
- Description updated (diff)
Updated by Helmut Hummel over 9 years ago
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
Applied in changeset 4bbdf7725b06ce2ed89d95217b6371ec40a0667a.
Updated by Benjamin Serfhos over 7 years ago
- Related to Bug #77645: Closures in SignalSlot\Dispatcher can cause troubles added
Updated by Riccardo De Contardi almost 7 years ago
- Status changed from Resolved to Closed