-
Notifications
You must be signed in to change notification settings - Fork 8
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
sfBrowser memory leak #2
Comments
Probably right, we would have to manually break the circular references. However since sfBrowser is only used for functional tests and this is not a critical bug for anything user-facing, it would have to be a clean fix with no impact on the API. |
Link is dead with reported issue -> can you state the issue please, I would like to take a look... |
The link is back up, but I'll copy paste here for posterity's sake: Original ticket:
Closed by fabien as wontfix on 06/14/09 16:31:08:
|
Was it really fixed in 5.3? On Tue, Jun 9, 2015 at 2:43 PM, Michael Kopinsky [email protected]
*THOMAS BOUTELL, *DEV & OPS |
I mean, yes, 5.3 gave PHP the ability to break circular references, but On Tue, Jun 9, 2015 at 2:58 PM, Tom Boutell [email protected] wrote:
*THOMAS BOUTELL, *DEV & OPS |
OK, I see Aaron's comment that PHP 5.3 doesn't help. Presumably each instance of sfBrowser adds itself to an array somewhere On Tue, Jun 9, 2015 at 2:43 PM, Michael Kopinsky [email protected]
*THOMAS BOUTELL, *DEV & OPS |
Fix for exception handling in PHP 7
The exact same issue as this ticket http://trac.symfony-project.org/ticket/6621
The ticket claims that PHP 5.3 fixes the issue, that is not the case.
The text was updated successfully, but these errors were encountered: