Uninitialized memory when loading invalid PNG data
Original reporter: Smitop
Area: Platform component
Creating a file with the contents "P3 50 50 255 0", and viewing it with "eog [file]" causes uninitialized memory to be displayed. The image is invalid due to not having enough pixel data, so an error should be shown instead. When using a larger size, like "P3 8000 8000 255 0", valgrind is able to detect the memory issues (but seemingly only sometimes?): https://paste.gnome.org/p2zootinp/gb4tyz
This seems to be an issue with gdk-pixbuf, which is used by eog to render images. This can be used to leak the contents of memory in applications that use gdk-pixbuf.