Bug 85064 – freetype memory leak

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 85064 - freetype memory leak

Summary:	freetype memory leak

Status:	CLOSED RAWHIDE

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	freetype (Show other bugs)
Sub Component:
Version:	9
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Owen Taylor
QA Contact:	Brock Organ
Docs Contact:

URL:
Whiteboard:
Keywords:

Duplicates:	85342 (view as bug list)
Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2003-02-25 03:41 EST by Havoc Pennington
Modified:	2007-04-18 12:51 EDT (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2003-06-09 17:37:44 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Havoc Pennington 2003-02-25 03:41:09 EST

Frederic says freetype leaks the whole gzip stream when loading compressed 
fonts... I haven't verified with our package.

<fcrozat> --- freetype-2.1.3/src/gzip/ftgzip.c.pix        2003-02-24
23:23:58.000000000 +0100
<fcrozat> +++ freetype-2.1.3/src/gzip/ftgzip.c    2003-02-24 23:26:22.000000000
+0100
<fcrozat> @@ -276,6 +276,8 @@
<fcrozat>    {
<fcrozat>      z_stream*  zstream = &zip->zstream;
<fcrozat>  
<fcrozat> +    inflateEnd(zstream);
<fcrozat> +
<fcrozat>      /* clear the rest */
<fcrozat>      zstream->zalloc    = NULL;
<fcrozat>      zstream->zfree     = NULL;

Comment 1 Owen Taylor 2003-02-28 10:00:09 EST

*** Bug 85342 has been marked as a duplicate of this bug. ***

Comment 2 Owen Taylor 2003-06-09 17:37:44 EDT

Was fixed in freetype-2_1_3-8

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