TYPO3 Core

I guess this might be happening as new objects are being generated which do not contain a UID yet. Could this be an issue?

Patch set 4 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/62722

Rejected due to the fact that this issue couldn't be reproduced by users. Feel free to reopen if this bug can be reproduced.

I was backtracing to out-of-memory issue and was able to fix this in my extension, which has a very complex data model with lots of relations.

It has a method getMyRelatedObjects in a Model to fetch myRelatedObjects but it does not return their ObjectStorage, instead it converts it to an array in order to sort it and creates a new ObjectStorage to add the related objects in the correct order:

    /**
     * @return \TYPO3\CMS\Extbase\Persistence\ObjectStorage<\Vendor\Extension\Domain\Model\MyRelatedObject>
     */
    public function getMyRelatedObjects() {
        $myRelatedObjects = ArraySort::sortByPropertyX($this->myRelatedObjects->toArray(), QueryInterface::ORDER_DESCENDING);

        $sortedStorage = new ObjectStorage();
        foreach ($myRelatedObjects as $myRelatedObject) {
            $sortedStorage->attach($myRelatedObject);
        }

        return $sortedStorage;
    }

Apparently extbase is calling the methods named like the properties by reflection during validation which causes these issues. By renaming the method getMyRelatedObjects to getMyRelatedObjectsSorted, adding a new getMyRelatedObjects method which simply returns the original $this->myRelatedObjects and switching all places where I need the related objects in a sorted order to use getMyRelatedObjectsSorted I was able to fix the memory issue.

I set this issue to rejected again as I cannot reproduce the issue of $validatorResults returning the SAME object(TYPO3\CMS\Extbase\Error\Result)#112081 for a second object anymore with current data.