DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:mime-version:content-type;
	b=KMgJGpzdr7/rB5tEAkSQFZUu/eu+MMTrFopdVewSO86sVHV2R8qbWvaGLGFIQBWqSb
	t+TWqtHCUigXc8MHtvHggO5wQVaeJQlyxVDAYukz+5Pe1CSUs6gan9kAuAbyy2fc6LRm
	c/60hbk3Dn8ICcvy5s9+CWdjfnu4YS9d9l94M=
Message-ID: <f74178430810271432p18464df9r854ce05c9bb714bb at mail.gmail.com>
Date: Mon, 27 Oct 2008 17:32:01 -0400
From: "Jacques Le Normand" <rathereasy at gmail.com>
To: lablgtk at yquem.inria.fr
MIME-Version: 1.0
Subject: [Lablgtk] memory leak resolved
Content-Type: multipart/mixed; boundary="===============0735523913=="
Mime-version: 1.0

--===============0735523913==
Content-Type: multipart/alternative; 
	boundary="----=_Part_28503_1900320.1225143121198"

------=_Part_28503_1900320.1225143121198
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

turns out the memory leak was in uim , not gtk
removing uim removed the problem

------=_Part_28503_1900320.1225143121198
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

turns out the memory leak was in uim , not gtk<br>removing uim removed the problem<br><br>

------=_Part_28503_1900320.1225143121198--


--===============0735523913==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Lablgtk mailing list
Lablgtk@yquem.inria.fr
http://yquem.inria.fr/cgi-bin/mailman/listinfo/lablgtk

--===============0735523913==--