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 678364 - Gimp crashes in 16-bit display mode
Gimp crashes in 16-bit display mode
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Backend: Win32
2.24.x
Other Windows
: Normal normal
: ---
Assigned To: gtk-win32 maintainers
gtk-bugs
: 692222 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2012-06-19 01:18 UTC by Tony
Modified: 2018-04-15 00:24 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Tony 2012-06-19 01:18:55 UTC 
When I was using the interface it crashed on me. It did it 3 or 4 times. I'm using windows vista on a laptop. I may try it on windows 7 to see if maybe it was just this OS. Thanks to everybody who contributes to this project.
Comment 1 Michael Schumacher 2012-06-19 05:14:29 UTC 
One common reason for that these days is that the display depth of your desktop is set to 16 bit instead of 32 bit.

Usually, there is no reason why it should be set to 16 bit, but maybe some game left in in this state. Please check that and report back.
Comment 2 Lars Christensen 2012-07-14 23:18:18 UTC 
I can confirm the Gimp Crash (Runtime Error) after running for just a few minutes in 16-bit color depths. Changed to 32-bits and it is now stable.

I noticed severe memory leaks when running with 16-bits colors. Just by continuously zooming (Ctrl + Scroll Wheel) the Gimp process would be over a gigabyte in just 10 seconds, and crash before reaching 2 GB (Win XP, 3GB system).
Comment 3 Max Mustermann 2012-09-04 20:02:30 UTC 
Confirming this for GIMP 2.8.2 in Win7, 32 bit as guest in Virtualbox.
In 16-bit color depth: after a few minutes, while painting with dynamics 'Confetti' GIMP crashes with the message 'Visual C++ runtime library: This application has requested the runtime to terminate in an unusal way. Please contact the applications support for more information.' It only happens, when the GIMP was started while already in 16-bit-color depth, but not after switching down from a higher color depth in a running GIMP session.
No problems in 24-bit or 32-bit color depth.
Comment 4 Jernej Simončič 2013-01-21 22:01:56 UTC 
*** Bug 692222 has been marked as a duplicate of this bug. ***
Comment 5 Michael Natterer 2013-08-23 21:51:42 UTC 
This was determined to be a GTK+ bug long ago.
Comment 6 Aleksander Morgado 2013-08-26 14:36:50 UTC 
I bet a beer this is a dup of bug 671538; which already has a working patch attached there.
Comment 7 Matthias Clasen 2018-02-10 05:05:12 UTC 
We're moving to gitlab! As part of this move, we are moving bugs to NEEDINFO if they haven't seen activity in more than a year. If this issue is still important to you and still relevant with GTK+ 3.22 or master, please reopen it and we will migrate it to gitlab.
Comment 8 Matthias Clasen 2018-04-15 00:24:43 UTC 
As announced a while ago, we are migrating to gitlab, and bugs that haven't seen activity in the last year or so will be not be migrated, but closed out in bugzilla.

If this bug is still relevant to you, you can open a new issue describing the symptoms and how to reproduce it with gtk 3.22.x or master in gitlab:

https://gitlab.gnome.org/GNOME/gtk/issues/new