Bug 603731 – Memory leak in Xvnc

Bug 603731 - Memory leak in Xvnc

Summary:	Memory leak in Xvnc

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	Red Hat Enterprise Linux 6
Classification:	Red Hat
Component:	tigervnc (Show other bugs)
Sub Component:
Version:	6.0
Hardware:	All Linux

Priority	low Severity medium
Target Milestone:	rc
Target Release:	---
Assigned To:	Adam Tkac
QA Contact:	Martin Cermak
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2010-06-14 09:06 EDT by Adam Tkac
Modified:	2010-11-10 16:47 EST (History)
CC List:	5 users (show)

See Also:
Fixed In Version:	tigervnc-1.0.90-0.8.20100115svn3945.el6
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2010-11-10 16:47:01 EST
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 Adam Tkac 2010-06-14 09:06:45 EDT

Description of problem:
There is a memory leak in Xvnc, check bug #597172 for more details. Patch should be backported.

Version-Release number of selected component (if applicable):
tigervnc-server-1.0.90-0.7.20100115svn3945.el6.x86_64

How reproducible:
always

Comment 3 RHEL Product and Program Management 2010-06-14 09:22:57 EDT

This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

Comment 4 Adam Tkac 2010-06-14 10:38:21 EDT

Fixed in tigervnc-1.0.90-0.8.20100115svn3945.el6.

Comment 8 Martin Cermak 2010-09-01 04:51:37 EDT

=> VERIFIED

Comment 9 releng-rhel@redhat.com 2010-11-10 16:47:01 EST

Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.

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