-
Notifications
You must be signed in to change notification settings - Fork 508
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
GraphIdentifiers don't seem to be cleaned-up #510
Comments
@mpdifran Who's able to help me on this? I don't know who the current contributors are, because I saw in an issue from 2020 that it looked like Swinject isn't maintained actively. |
CC @yoichitgy Maybe you can help? |
I'll flag this to the contribution group! We are trying to continue maintaining this actively, and we've extended our contributors to help with that. |
Some additional information: I've got a set of structs conforming to
I'll then have a property |
@mpdifran @yoichitgy Can you confirm that my previously sent message contains a correct setup for Swinject? |
@jbehrens94 yeah your setup looks correct, I don't see anything wrong with it. |
What could be causes for Swinject to keep graph identifiers in memory and not clean up? |
Same question for the Swinject.(Weak..) things |
I investigated this a little, and from what I can tell, the Edit: On platforms with the Objective-C runtime, this is available as |
Hi all,
I'm working on an app extension with extremely limited resources in terms of memory. I noticed that Swinject is claiming a lot of memory through
GraphIdentifier
, it'll increase quite a lot when doing regular actions throughout the extension.Am I using Swinject wrong, or what should I do to minimise that amount in memory?
The text was updated successfully, but these errors were encountered: