ImageShader should have a dispose method, and it should be called by the framework.

[dnfield]

Image Shaders, particularly those that end up creating an SkImageShader, can hold substantial amounts of memory.

As we wire up methods to make sure we dispose of Layer objects and related memory, we should make sure we dispose of these as well.

see also #81514, #57746

[dnfield]

/cc @flar @LongCatIsLooong who might have good opinions on this

[dnfield]

While we're at it, we should fix _ImageFilter so that it doesn't call two native methods to initialize itself.

[dnfield]

I think what we really want is for ImageShader to have a dispose method. ImageFilter was the wrong thing here. I will re-purpose this bug for that, since AFAICT we don't really tie much int he way of native resources to ImageFilters.

[dnfield]

I was just wrong about filters. They're really pretty light weight and they can't really dispose anything - this only applies to image shaders.

[dnfield]

And the framework does not use image shader anywhere AFAICT.

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.