@nicolas-grekas so you would still get a silent hard failure if you doc:c --env prod?

Not since 10 minutes. When did you read the code ? :)

I didn't, but I have trouble following :P

Fwiw, I believe a user on Twitter hit the same issue - when removing Twighttps://twitter.com/neelion333/status/936623941937795072 - looks very easy to reproduce

I think this bug might be quite critical. I think I'm even able to hit it through the web interface. While upgrading a project from 3.3 to 3.4, I did the following:

1. Added thecontainer.autowiring.strict_mode: true parameter.
2. Refreshed to rebuild the container
3. Removed this parameter
4. Refreshed to this error:

@nicolas-grekas Do you think it's related? Do you need me to try to create a repeater (the above was done on our big KnpU Symfony 3 tutorial project).

@weaverryan looks like the same yes.

I improved the behavior by replacing the nasty@-silencing by a specificE_WARNING silencing. The container-loading file is also now resilient to a broken container folder, by using include+return in case of failure. Also handled by Kernel.

PR is ready. Dunno how to test it as the behavior is triggered by edge case fatal errors...

Thank you@nicolas-grekas.

I do not appear to be able to trigger the fatal error anymore. I think you may have gotten it!

I experienced this bug today usingSymfony 4.0.6. It occurs in certain controller actions and not when using the cache commands via terminal. But these actions call indirectlycache->clear() which seem to interfere with symfony internals?

FatalErrorException Compile Error: Container Failed opening required [...]getRouting_LoaderService.php' (include_path='.:/usr/local/lib/php') in srcDevDebugProjectContainer.php (line 295)

I was able to "fix" that for now, byremoving the WebProfilerBundle resp.ProfilerPack:

• "symfony/profiler-pack": "^1.0"
• "symfony/web-profiler-bundle": "^4.0.6"

Afterwards i cleared the cache usingrm -rf var/cache/* and it seems to work.

EDIT: See#25255 (comment) for updates to the WebProfilerBundle.

What are you calling in your controller?

Here is part of the code:

$env =/* .. */;$cache =newFilesystemCache('',0,__DIR__.'/../../var/cache/'.$env);// do some mysql operations$cache->clear();

I expected the cache, because you mentioned it at the beginning. Furthermore, it tried to load something from the cache folder, which could not be opened.

FatalErrorException Compile Error: Container Failed opening required [...]getRouting_LoaderService.php' (include_path='.:/usr/local/lib/php') in srcDevDebugProjectContainer.php (line 295)

Ok, i changed$cache->clear() to a solution which directly removes entries, which my app created. I re-enabled the WebProfilerBundle and tried the mentioned controller actions. And it worked. I assume, that calling$cache->clear() in a controller was the problem?

I suppose. FilesystemCache is not made for clearing the full Symfony cache AFAIK.