From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-0.3 required=5.0 tests=BAYES_00, REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4 X-Google-Thread: 103376,884d34d0342bc569 X-Google-NewGroupId: yes X-Google-Attributes: gida07f3367d7,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Received: by 10.68.223.73 with SMTP id qs9mr1729385pbc.7.1341147326695; Sun, 01 Jul 2012 05:55:26 -0700 (PDT) Path: l9ni6048pbj.0!nntp.google.com!news1.google.com!npeer01.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!nx01.iad01.newshosting.com!newshosting.com!87.79.20.101.MISMATCH!newsreader4.netcologne.de!news.netcologne.de!news.mixmin.net!aioe.org!.POSTED!not-for-mail From: "Dmitry A. Kazakov" Newsgroups: comp.lang.ada Subject: Re: memory leak with new GPS in GNAT GPL 2012 on Windows Date: Sun, 1 Jul 2012 14:55:25 +0200 Organization: cbb software GmbH Message-ID: <1462rs8dcy2e9.1wn7m6k817a6c$.dlg@40tude.net> References: <36ae3508-2a3e-4cf7-b884-ea1873b2a2f5@googlegroups.com> <0513685d-9db7-4df9-8592-a463ccd175e9@googlegroups.com> <32f6a8d4-088b-4b9f-b390-16743672f56a@googlegroups.com> Reply-To: mailbox@dmitry-kazakov.de NNTP-Posting-Host: 9A8bJrx4NhDLcSmbrb6AdA.user.speranza.aioe.org Mime-Version: 1.0 X-Complaints-To: abuse@aioe.org User-Agent: 40tude_Dialog/2.0.15.1 X-Notice: Filtered by postfilter v. 0.8.2 X-Received-Bytes: 1619 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Date: 2012-07-01T14:55:25+02:00 List-Id: On Sun, 1 Jul 2012 03:51:09 -0700 (PDT), francois_fabien@hotmail.com wrote: > Since GPS is using GTK, and GTK has a loop, I would think that this loop is leaking. It is probably this: http://stackoverflow.com/questions/10837776/memory-leak-in-gtk-under-windows-7-in-gtk-widget-queue-draw The bug is in GTK itself, which leaks upon queueing window refresh requests. Presumably GTK does not free some Windows GDI resources. We have no better choice that to wait for GTK going 3.x under Windows and see if the bug is still there. -- Regards, Dmitry A. Kazakov http://www.dmitry-kazakov.de