LibXcursor is leaking memory

Solution Verified - Updated -

Issue

A memory leak has been detected in libXcursor with any Xt or Openmotif program running under Valgrind:

==3210== 60 bytes in 1 blocks are definitely lost in loss record 386 of 724  
==3210==    at 0x4A05E1C: malloc (vg_replace_malloc.c:195)  
==3210==    by 0x3403C05495: _XcursorFileHeaderCreate (file.c:219)  
==3210==    by 0x3403C05CB7: _XcursorReadFileHeader (file.c:255)  
==3210==    by 0x3403C066C8: XcursorXcFileLoadImages (file.c:659)  
==3210==    by 0x3403C067E8: XcursorFileLoadImages (file.c:948)  
==3210==    by 0x3403C07074: XcursorLibraryLoadImages (library.c:311)  
==3210==    by 0x3403C079A7: XcursorTryShapeCursor (xlib.c:106)  
==3210==    by 0x33FFC250B3: XCreateGlyphCursor (CrGlCur.c:175)  
==3210==    by 0x33FFC25610: XCreateFontCursor (Cursor.c:52)  
==3210==    by 0x340D81A3F0: XtCvtStringToCursor (Converters.c:688)  
==3210==    by 0x340D815953: CallConverter (Convert.c:808)  
==3210==    by 0x340D815CDB: _XtConvert (Convert.c:896)

Environment

  • Red Hat Enterprise Linux 5 (RHEL)
  • libXcursor

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content