You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
changed the title [-][Bug]: High memory usage by `Figure.savefig` starting in version 3.10.0[/-][+][Bug]: High memory usage by `Figure.savefig`[/+]on Jan 8, 2025
Would it be worth adding #28061, the image resampling docs, and this workaround to the 3.10 release notes? I could see this affecting quite of bit of code with non-obvious slowdowns and OOM errors (which is how I found it in the first place 🙂).
Activity
[-][Bug]: High memory usage by `Figure.savefig` starting in version 3.10.0[/-][+][Bug]: High memory usage by `Figure.savefig`[/+][-][Bug]: High memory usage by `Figure.savefig`[/-][+][Bug]: High memory usage in `Figure.savefig`[/+]QuLogic commentedon Jan 9, 2025
This bisects to 3ceba40; you can set
image.interpolation_stagetodatato avoid it switching to thergbastage.zqianem commentedon Jan 9, 2025
Thanks for tracking this down!
Would it be worth adding #28061, the image resampling docs, and this workaround to the 3.10 release notes? I could see this affecting quite of bit of code with non-obvious slowdowns and OOM errors (which is how I found it in the first place 🙂).
tacaswell commentedon Jan 9, 2025
Some what ironically, the big images are where the RGBA interpolation is probably the most useful.
jklymak commentedon Jan 9, 2025
Yeah, I'm not quite sure why that is not in the release notes. Sorry for not catching that it was missing.