Thanks for making my point, the program is indeed opening individual frames.
And what are you on about after that? No one said it's unsurprising for that to cause a bug. It's saying that the gif is not cause here, an editor is coming across a framework call that's blowing up
Call it an editor bug, or a framework bug, it's not an image using the memory, it's the editor
Oh my god. I get it. You’re reading the headline as “this GIF uses xx memory”. That’s not what is says. It’s “GIF uses X memory on x86, X*10 memory on M1”. You’re picking a fight based on your own misreading.
And what are you on about after that? No one said it's unsurprising for that to cause a bug. It's saying that the gif is not cause here, an editor is coming across a framework call that's blowing up
Call it an editor bug, or a framework bug, it's not an image using the memory, it's the editor