Bug 1007841

Summary:	Leak 16 MB of memory per connection opened
Product:	Red Hat Enterprise Linux 7	Reporter:	Daniel Berrangé <berrange>
Component:	spice-gtk	Assignee:	Marc-Andre Lureau <marcandre.lureau>
Status:	CLOSED ERRATA	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.0	CC:	dblechte, marcandre.lureau, mkrcmari, rbalakri
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	spice-gtk-0.22-1.el7	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1007837	Environment:
Last Closed:	2015-03-05 13:40:36 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1028637, 1109397
Bug Blocks:

Description Daniel Berrangé 2013-09-13 12:45:39 UTC

spice-gtk copied the gtk-vnc coroutine_ucontext.c so suffers from this same flaw

+++ This bug was initially created as a clone of Bug #1007837 +++

Description of problem:
The ucontext coroutine implementation mmap()s 16 MB of memory for the coroutine stack, but fails to ever unmap it. This causes the stack to leak for each coroutine started

Version-Release number of selected component (if applicable):
gtk-vnc-0.5.2-2.el7

How reproducible:
Always


Steps to Reproduce:
1. Run demo program in https://bugzilla.gnome.org/show_bug.cgi?id=705827 it will consume memory until exhausted, then crash.
2.
3.

Comment 1 Daniel Berrangé 2013-09-13 12:55:01 UTC

Two patches for this sent upstream:

http://lists.freedesktop.org/archives/spice-devel/2013-September/014522.html
http://lists.freedesktop.org/archives/spice-devel/2013-September/014520.html

Comment 4 Marc-Andre Lureau 2014-07-08 15:47:39 UTC

please QA ack, this is included in rebase

Comment 8 errata-xmlrpc 2015-03-05 13:40:36 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-0297.html