Bug 19359 - assertion `image != NULL' failed.
Summary: assertion `image != NULL' failed.
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: gnome-libs
Version: 7.3
Hardware: alpha
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Elliot Lee
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-10-19 01:30 UTC by Michal Jaegermann
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2000-10-19 18:43:46 UTC
Embargoed:


Attachments (Terms of Use)

Description Michal Jaegermann 2000-10-19 01:30:50 UTC
Every time gnome-terminal is opened (do that from another terminal to see
messages) the following shows up:

Gdk-CRITICAL **: file gdkimage.c: line 416 (gdk_image_destroy): assertion
`image != NULL' failed.

Gdk-CRITICAL **: file gdkimage.c: line 416 (gdk_image_destroy): assertion
`image != NULL' failed.

Gdk-CRITICAL **: file gdkimage.c: line 416 (gdk_image_destroy): assertion
`image != NULL' failed.

Gdk-CRITICAL **: file gdkimage.c: line 416 (gdk_image_destroy): assertion
`image != NULL' failed.


Should this Gdk-CRITICAL be not considered seriously?

  Michal
  michal

Comment 1 David Mason 2000-10-19 14:57:38 UTC
hp - I cannot reproduce, can you? --- michal
, prehaps try version on the released RH7 instead of the beta.


Comment 2 Havoc Pennington 2000-10-19 15:52:13 UTC
I can't reproduce it either; need more info on how to make it happen.

Comment 3 David Mason 2000-10-19 18:09:35 UTC
can reproduce on some alphas and not on others... reassigning to Sopwith... he
has an alpha :)


Comment 4 Michal Jaegermann 2000-10-19 18:43:40 UTC
Oh, in that case this is probably a type bug somewhere in a library. 
An intention is to check 'long', or a pointer, a value stuck there comes
as 'int' and the upper half of a value has in it a random garbage which
sometimes is zero and sometimes is not.  This is a _guess_!!

CRITICAL does not seem to be that critical as things appear to work just
fine after this initial noise.

Comment 5 Elliot Lee 2000-10-19 20:40:14 UTC
The warnings are generated because of incorrect error handling
in gtk+. I've fixed the error handling.

There is a separate issue with shared memory on the Alpha that makes these error
handlers even get hit, which is already being solved.


Note You need to log in before you can comment on or make changes to this bug.