-
Notifications
You must be signed in to change notification settings - Fork 211
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
Potential memory leak with AnimatedImage with a context menu modifier on macOS #253
Comments
AnimatedImage (actually, it use a UIViewRepresentable This does not works on macOS seems (The But it's not a "leak" in general, if you totally make your LazyGrid disappear, the cache frame should be free. |
Can you provide a Xcodeproject demo for me to investigate ? I did not have a real-formed macOS App to use LazyVGrid. |
Here is a Xcode project demo that basically demonstrates the issue. I am pulling the images from a remote source (Giphy) and the issue described above still occurs. https://github.com/andylin2004/TestGifVGridApp |
I have a SwiftUI multiplatform project where I have a
ScrollView
containing aLazyVGrid
, which contains a bunch of VStacks containing aAnimatedImage
s, all of which are given thepurgeable(true)
,pausable(false)
,resizable()
, andscaledToFit()
modifier, and aText
. TheVStack
is given acontextMenu
modifier that passes in a text, button, or a combination of the two (the text and/or buttons could be wrapped in a view and the same thing would happen).On iOS, if I activate the context menu (by long pressing on the
VStack
), there isn't a spike in RAM use. However, on macOS, if I activate the context menu (by clicking on theVStack
with two fingers), the RAM use spikes and never drops down at all, indicating a memory leak issue. I'm not too sure how this is happening, but I have a suspicion that there is something to do with either macOS's implementation of aLazyVGrid
or howAnimatedImage
is implemented on macOS.The text was updated successfully, but these errors were encountered: