Everything works fine with symfony\symfony v2.3.13, bug is in v2.3.14

I have got a similar issue with both 2.4.5 and 2.5.0, which seems linked to #10894.

For performance reason related to VBox shared folders, vendor/, cache/ and logs/ have been moved out of the application folder (one level higher). I have got the same error than @covex-nn, caused by getTwig_LoaderService in cache/dev/appDevDebugProjectContainer.php.

I have found to the following workaround, by changing how the cache and log paths are configured in app/AppKernel.php:

Before:

    public function getCacheDir()
    {
        return __DIR__.'/../../cache/'.$this->environment;
    }

    public function getLogDir()
    {
        return __DIR__.'/../../log/';
    }

After:

    public function getCacheDir()
    {
        return dirname(dirname(__DIR__)).'/cache/'.$this->environment;
    }

    public function getLogDir()
    {
        return dirname(dirname(__DIR__)).'/log/';
    }

We are also experiencing this issue indirectly, due to the di extra bundle which has a cache warmer for warming up controller annotations. The changes from 2.3.13 to 2.3.14 of converting dumped container paths to absolute seem to indirectly cause the controller file paths you blacklist from di to be modified and then they do not match the paths to the controllers anymore.

Regular expression replaces ROOT_PATH with __DIR__ everywhere in the original path, not only in the begining or after file:

Is there any other path variations except those in https://github.com/symfony/symfony/blob/2.3/src/Symfony/Component/HttpKernel/Tests/Fixtures/DumpedContainers/app/cache/dev/withAbsolutePaths.php file ? Can original path has another prefix (not file:) ?

We also ran into this. The kernel.root_dir that gets injected (since v2.3.14) is screwed up for everything, so you can no longer rely on it in your own service configs.

Does #10979 fix the issue?

For us the issue is that kernel.root_dir now contains /path/to/app/cache/environment/../.. instead of just /path/to/app. We used dirname on it to get to the actual project dir, and these calls all break on the relative paths that are returned now (as of 2.3.14). Wrapping it in realpath solved our issue (well, we had to do either that or use a getRootDir() call on the kernel instead which does actually still return the realpath of the root dir)...

@covex-nn looks like what you mention is exactly the fix done in #10979.

@fabpot no, it does not

Let say, that kernel.root_dir is /vagrant/symfony/src/Symfony/Component/HttpKernel/Tests/Fixtures/DumpedContainers/app and composer.json is located in /vagrant/symfony/src/Symfony/Component/HttpKernel/Tests/Fixtures/DumpedContainers/app.

Then removeAbsolutePathsFromContainer function will replace '/some/where/else/foo/vagrant/symfony/src/Symfony/Component/HttpKernel/Tests/Fixtures/DumpedContainers' with '/some/where/else/foo'.__DIR__.'/../../..'

I mean, if some path contains path to composer.json somewhere in the middle, then it will be replaced by __DIR__ with dots in removeAbsolutePathsFromContainer

I made a mistake in my first commit, so I updated test and fixtures. Please see https://github.com/covex-nn/symfony/commit/679075e1af88b9298bcae5f06f38b11286cf729d

Here is PHPUnit output:

There was 1 failure:

1) Symfony\Component\HttpKernel\Tests\KernelTest::testRemoveAbsolutePathsFromContainer
Failed asserting that two strings are equal.
--- Expected
+++ Actual
@@ @@
 '/some/where/else/foo'
-'/some/where/else/foo/vagrant/symfony/src/Symfony/Component/HttpKernel/Tests/Fixtures/DumpedContainers'
+'/some/where/else/foo'.__DIR__.'/../../..'

 'file:'.__DIR__.'/profiler'
 '

/vagrant/symfony/src/Symfony/Component/HttpKernel/Tests/KernelTest.php:842

The code has been reverted for now. See #10999 for more information.