From: Hans-Werner Hilse <hilse@web.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] memory leak with gtk+-2.8.20-r1
Date: Wed, 2 Aug 2006 18:24:58 +0200 [thread overview]
Message-ID: <20060802182458.7b59bd59.hilse@web.de> (raw)
In-Reply-To: <pan.2006.08.02.16.14.00.910025@free.fr>
Hi,
On Wed, 02 Aug 2006 18:14:02 +0200
gwe <gwenjo@free.fr> wrote:
> > Ah yes, I wasn't aware that there was a function for this. You should
> > definitely use this in place of the delete statement because it will do
> > deeper cleaning.
>
> the GTK Api said gtk_exit is deprecated and should not be used.
> In fact, i'm very astonished because it's not the first software with GTK
> I wrote but it's the first time that I have this problem.
> It's so recent
OK, I didn't counter-check it and was probably reading some outdated
documentation. I was just searching for some kind of cleanup function
and thought I found it. So it's probably in fact a gtk memory leak. Are
you by chance running non-x86? That might explain why it passed some
tests though buggy on that arch...
OK, I'm out of suggestions :-) Maybe a manual delete would help, but I
somehow doubt that (cleanup is probably done by gtk_main_quit() now?)
-hwh
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-08-02 16:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6FnoP-4ZX-69@gated-at.bofh.it>
[not found] ` <6FnoP-4ZX-71@gated-at.bofh.it>
[not found] ` <6FnoP-4ZX-67@gated-at.bofh.it>
[not found] ` <6FpgY-7RO-5@gated-at.bofh.it>
[not found] ` <6FqPE-1YI-3@gated-at.bofh.it>
2006-08-02 16:14 ` [gentoo-user] memory leak with gtk+-2.8.20-r1 gwe
2006-08-02 16:24 ` Hans-Werner Hilse [this message]
[not found] <6FmCn-3KJ-17@gated-at.bofh.it>
[not found] ` <6FmVF-4oe-19@gated-at.bofh.it>
2006-08-02 11:49 ` gwe
2006-08-02 13:47 ` Hans-Werner Hilse
2006-08-02 15:20 ` Randy Barlow
2006-08-02 11:04 gwe
-- strict thread matches above, loose matches on Subject: below --
2006-08-02 10:58 gwe
2006-08-02 11:16 ` Hans-Werner Hilse
2006-08-02 15:14 ` Randy Barlow
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060802182458.7b59bd59.hilse@web.de \
--to=hilse@web.de \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox