Bug #47331
ObjectManager shutdown with Dependency Injection Proxy causes fatal errors
| Status: | Accepted | Start date: | 2013-04-17 | |
|---|---|---|---|---|
| Priority: | Must have | Due date: | ||
| Assigned To: | - | % Done: | 0% |
|
| Category: | Object | |||
| Target version: | TYPO3 Flow Base Distribution - 2.0.1 | |||
| PHP Version: | Complexity: | |||
| Has patch: | No | Affected Flow version: | Git 2.0 |
Description
I observed this when testing an application through Behat as a normal result that returned a 500 status code. Must be introduced between 903271f and f5b5024.
Uncaught exception in line 398 of .../FlowRoot/Packages/Framework/TYPO3.Flow/Classes/TYPO3/Flow/Object/ObjectManager.php: Object not found - See also: 2013
04171927569fb730.txt
----
Uncaught exception in line 398 of .../FlowRoot/Packages/Framework/TYPO3.Flow/Classes/TYPO3/Flow/Object/ObjectManager.php: Object not found
8 SplObjectStorage::offsetGet(TYPO3\Flow\Object\DependencyInjection\DependencyProxy)
7 TYPO3\Flow\Object\ObjectManager::shutdown("Runtime", "TYPO3\Flow\Core\Bootstrap::bootstrapShuttingDown", "TYPO3\Flow\Core\Bootstrap::bootstrapShuttingDown")
6 call_user_func_array(array|2|, array|3|)
5 TYPO3\Flow\SignalSlot\Dispatcher::dispatch("TYPO3\Flow\Core\Bootstrap", "bootstrapShuttingDown", array|1|)
4 TYPO3\Flow\Core\Bootstrap::emitBootstrapShuttingDown("Runtime")
3 TYPO3\Flow\Core\Bootstrap::shutdown("Runtime")
2 TYPO3\Flow\Http\RequestHandler::handleRequest()
1 TYPO3\Flow\Core\Bootstrap::run()
History
#1 Updated by Robert Lemke over 2 years ago
- Target version set to 2.0
Sounds like the ObjectManager should just omit this - if it finds an object "DependencyProxy" there's no need to call its shutdown method, because it hasn't even been initialized. Actually cool optimization ...
#2 Updated by Robert Lemke about 2 years ago
- Status changed from New to Accepted
- Target version changed from 2.0 to 2.0.1