| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
When loading an invalid image with a missing EOI marker we end up
triggering an infinite loop inside libjpeg.
Original patch by: Sam Ezeh <sam.z.ezeh@gmail.com>
Fixes: #209
|
| |
|
| |
|
|\
| |
| |
| |
| | |
build: Clean up search for deps on Visual Studio
See merge request GNOME/gdk-pixbuf!131
|
| |
| |
| |
| |
| | |
Like the previous commits, use CMake's builtin support to look for
libtiff, which will clean things up a bit in the build files
|
| |
| |
| |
| |
| |
| |
| | |
Like wat we did for libpng, do likewise to look for libjpeg (or
libjpeg-turbo) via CMake's builtin support, so that we can clean up the
build files and have CMake do a more comprehensive manual search for
libjpeg or libjpeg-turbo.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We can use CMake's built-in search for the libpng headers and libraries
for Visual Studio-like compilers; however, we must use 'png' instead of
'libpng' for the package name for this to work.
This will cover the manual headers and .lib search in a more
comprehensive way, which CMake will handle for us and it is an
optionally-installed item for Visual Studio 2017 and later, and is very
commonly used on Windows dev environments.
Also use a common variable to indicate whether we are using an MSVC-like
compiler, to save future typing.
|
|\ \
| | |
| | |
| | |
| | | |
Disable relocation when built as a static libary on Windows
See merge request GNOME/gdk-pixbuf!136
|
| | | |
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
meson: update man option to mention it now requires rst2man
See merge request GNOME/gdk-pixbuf!135
|
| |/ / |
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
jpeg: Limit the memory size when loading image data
Closes #205
See merge request GNOME/gdk-pixbuf!139
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Specially crafted JPEG images may lead to a crash when their size is too
large; in the most benign of cases, the OS might terminate the process
after it tries to allocate all the memory in the world.
We can tell libjpeg to limit the size of the memory pool when loading,
to avoid this kind of result. For the time being, 100 MB seems like a
good threshold.
Original patch by: Sam Ezeh <sam.z.ezeh@gmail.com>
Fixes: #205
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
Fix overflow when reading GIF images with invalid LZW initial code size.
See merge request GNOME/gdk-pixbuf!130
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This value is the number of bits for each symbol (i.e. colour index) decoded via LZW.
The maximum LZW code is specified as 12 bits, so the value here can only be 11 as two additional code words are required (clear and end of information) that immediately uses an additional bit.
This implementation has always been wrong, and the Firefox implementation has the same issue so it seems a common misinterpretation of the spec.
This has been changed here to avoid an assertion later in the LZW decoder.
Note that there is never any reason for a GIF to be encoded with more than 8 bits of colour information, as the colour tables only support up to 8 bits.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
build: Update libjpeg-turbo wrap
See merge request GNOME/gdk-pixbuf!138
|
|/ / / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The current wrap version has a bug when building on Windows with
MSVC. Update to 2.1.2-2 as per wrapdb [1].
[1]
https://wrapdb.mesonbuild.com/v2/libjpeg-turbo_2.1.2-2/libjpeg-turbo.wrap
|
| | | | |
|
| |/ /
|/| | |
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
Replace DocBook with reStructuredText for man pages
See merge request GNOME/gdk-pixbuf!134
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
For rst2man.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The dependency on xsltproc and the DocBook style sheets is vaguely
annoying, and there are better tools these days that do not require
writing XML.
|
|\ \ \ \
| |/ / /
|/| | |
| | | |
| | | | |
meson: add build_tests option
See merge request GNOME/gdk-pixbuf!132
|
|/ / / |
|
|\ \ \
| |_|/
|/| |
| | |
| | | |
ci: Disable man pages on MSYS2
See merge request GNOME/gdk-pixbuf!133
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The macOS CI runner is really flaky, so we can't allow it to block every
time it goes belly up.
See also: https://gitlab.gnome.org/Infrastructure/GitLab/-/issues/558
|
|/ /
| |
| |
| |
| | |
Otherwise we need docbook-xsl stylesheets for turning docbook into man
pages.
|
| | |
|
| | |
|
|/ |
|
| |
|
| |
|
|\
| |
| |
| |
| |
| |
| | |
gdk_pixbuf_new() - Clear the pixbuf's memory buffer to avoid returning uninitialized memory
Closes #199
See merge request GNOME/gdk-pixbuf!128
|
|/
|
|
|
|
| |
uninitialized memory
Fixes https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/199
|
| |
|
|\
| |
| |
| |
| | |
docs: Fix the XPM data annotation
See merge request GNOME/gdk-pixbuf!125
|
| |
| |
| |
| | |
The return value of GdkPixbufModuleBeginLoadFunc is NULL only on error.
|
|/
|
|
| |
Make sure that the array is annotated as zero-terminated.
|
|\
| |
| |
| |
| | |
Turn GdkPixbufModule functions into typed callbacks
See merge request GNOME/gdk-pixbuf!123
|
| |
| |
| |
| | |
This way we can properly document and annotate them.
|
|\ \
| | |
| | |
| | |
| | | |
tiff: Use non-deprecated C99 integer types
See merge request GNOME/gdk-pixbuf!124
|