GraphQLBundle
GraphQLBundle copied to clipboard
fix: Fix the memory leak
Q | A |
---|---|
Bug fix? | yes |
New feature? | no |
BC breaks? | no |
Deprecations? | no |
Tests pass? | could not check |
Documented? | no |
Fixed tickets | #721 |
License | MIT |
Follow up of my comment.
I cannot investigate further, but my guess is that exceptions are not cheap objects. When creating an exception you also capture the context and stack trace which means that even if the extension is unsued:
- It slows down the program because instantiating it is not cheap.
- May prevent some objects to be garbage collected because referenced in the exception.
Hi @theofidry! Can you check the tests please? Don't have time to dig into this atm but it seems to break the tests suite: https://github.com/overblog/GraphQLBundle/pull/1119/checks
Thanks!
Hi @theofidry! Any update on this topic? Thanks!
Sorry will try to come back to this in a near future