Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[HttpKernel][Config][FileLocator] Multiple kernel initializations #2821

Closed
lisachenko opened this issue Dec 9, 2011 · 1 comment

Comments

Projects
None yet
2 participants
@lisachenko
Copy link

commented Dec 9, 2011

There are multiple kernel initializations during unserialization of FileLocator object as it stores link to the kernel. So when cache metadata is unserialized then some more instances of kernel will be created.

Here trace for this:

Symfony\Component\Routing\Router->getMatcher()
Symfony\Component\Config\ConfigCache->isFresh(..)
unserialize(...O:47:"Symfony\Component\HttpKernel\Config\FileLocator":3:{s:55:"�Symfony\Component\HttpKernel\Config\FileLocator�kernel";C:9:"AppKernel":28:{a:2:{i:0;s:3:"dev";i:1;b:1;}}....)
Symfony\Component\HttpKernel\Kernel->unserialize(a:2:{i:0;s:3:"dev";i:1;b:1;})
AppKernel->__construct(dev, 1)

So, need to remove a link to the kernel during serialization of FIlelocator and need to take existing instance of Kernel during unserialization.

@fabpot

This comment has been minimized.

Copy link
Member

commented May 7, 2012

This is a bug in AsseticBundle as the AsseticResource depends on many objects. I'm moving this issue there: symfony/assetic-bundle#80.

@fabpot fabpot closed this May 7, 2012

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.