#55029Class Loader fails if entry in class cache is discarded
Description
Steps to reproduce:
- rm -rf typo3temp/Cache/
- do a (e.g. FE-) request to populate caches
- rm typo3temp/Cache/Data/cache_classes/psr_log_loggerinterface
After that you get a fatal error for every request.
This is the case because autoload registry and aliases only populate this cache if the package states change.
Having a volatile cache for cache_classes (like memcache or APC) will sooner or later lead to a fatal error, which is not acceptable.
Idea: Introduce a two level cache for cache_classes that has persistent (file) second level cache and a potentially volatile and fast first level cache.
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
Related issues 5
- Bug #54004Extension checker does not use the autoloader?
- Bug #54906Fatal error: Interface 'Psr\Log\LoggerInterface' not found
- Task #54984"Clear all caches" makes the site unavailable for several seconds
- Task #54990ClassLoader cache ist too slow, no matter which CF Backend is used
- Bug #55099PHP Warnings after clearing configuration cache in BE