After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 583547 - gdk_pixbuf_loader_get_pixbuf returns different results if gdk_pixbuf_loader_set_size has been called
gdk_pixbuf_loader_get_pixbuf returns different results if gdk_pixbuf_loader_s...
Product: gdk-pixbuf
Classification: Platform
Component: general
git master
Other Linux
: Normal normal
: ---
Assigned To: gdk-pixbuf-maint
Depends on:
Reported: 2009-05-22 12:21 UTC by Andrey Tsyvarev
Modified: 2018-05-22 13:10 UTC
See Also:
GNOME target: ---
GNOME version: ---

Example that demonstrates problem (1.59 KB, text/plain)
2009-05-22 12:22 UTC, Andrey Tsyvarev
image used in example (29.35 KB, image/bmp)
2009-05-22 12:23 UTC, Andrey Tsyvarev

Description Andrey Tsyvarev 2009-05-22 12:21:32 UTC
Values, returned by gdk_pixbuf_loader_get_pixbuf before and after call of gdk_pixbuf_loader_close, may differ. This difference contradict to the description of gdk_pixbuf_loader_get_pixbuf:

The returned pixbuf will be the same in all future calls to the loader, so simply calling g_object_ref() should be sufficient to continue using it.

This occures when gdk_pixbuf_loader_set_size has been called with sizes which different from sizes of image loaded.
Comment 1 Andrey Tsyvarev 2009-05-22 12:22:48 UTC
Created attachment 135168 [details]
Example that demonstrates problem
Comment 2 Andrey Tsyvarev 2009-05-22 12:23:46 UTC
Created attachment 135169 [details]
image used in example
Comment 3 Bastien Nocera 2014-10-22 13:07:04 UTC
I can reproduce this with gdk-pixbuf 2.31, and not just with the BMP loader, but with the PNG one too.
Comment 4 GNOME Infrastructure Team 2018-05-22 13:10:33 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: