Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

For bugs related to Red Hat Enterprise Linux 4 product line. The current stable release is 4.9. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 189165

Summary:	GD temp files are not deleted
Product:	Red Hat Enterprise Linux 4	Reporter:	Martin Sarsale <martin>
Component:	php	Assignee:	Joe Orton <jorton>
Status:	CLOSED DUPLICATE	QA Contact:	David Lawrence <dkl>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.0
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2006-12-14 15:41:43 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Martin Sarsale 2006-04-17 19:17:22 UTC

From php tracker:

Description:
------------
A temprorary file is create in gd.c line 1667.  This file is never
deleted.  Today I found 10 thousand files in /tmp on each server.

A comment on line 1720 says 

"the temporary file is automatically deleted" 

However, this is not the case.  I can't find any code anywhere that
would delete the tmp file.  I also checked the lastest cvs. 

Fix: 

I fixed the problem by rolling back to gd.c version 1.221.2.44 which
works for me.

Comment 1 Joe Orton 2006-12-14 15:31:43 UTC

Can you give a reproduction case for this temporary file leak?  A temporary file
leak was fixed in php-4.3.9-3.10 and later in the GIF output paths; perhaps this
was the bug in question.

Comment 2 Martin Sarsale 2006-12-14 15:37:58 UTC

yes, I think it was
someone answer that in IRC like 8 months ago.
thanks anyway

Comment 3 Joe Orton 2006-12-14 15:41:43 UTC

Thanks; sorry for the slow response.

*** This bug has been marked as a duplicate of 182719 ***