Hi,
Christoph Kappel [EMAIL PROTECTED] writes:
I will try to make a text case later, guess the leak occurs only in
conjunction with the GIOChannels. I don't use any GStrings in my
project, except the GString buffer from the GIOChannels. Closing the
channel und flushing the buffer should be
On 02 Dec 2003 15:56:57 +0100
Sven Neumann [EMAIL PROTECTED] wrote:
Simple. Make sure you release all resources you are allocating. You
could use memprof or valgrind to find out where you are leaking
memory. Of course it is possible but very unlikely that the libraries
itself are leaking
On Tue, 2 Dec 2003 19:48:12 +0100
[EMAIL PROTECTED] wrote:
Make sure that you are using the latest gtk 2.2.x. I remember a very
significant GIOChannel memory bug that Daniel Elstner fixed about a
year ago.
Then try to make a small test case for bugzilla.
I am using gtk+ 2.2.4, so it should
I am using gtk+ 2.2.4, so it should be the last stable
release. Every time when i use any GString / function i get leakage.
Then try to make a small test case for bugzilla.
Murray Cumming
www.murrayc.com
[EMAIL PROTECTED]
___
gtk-list mailing list
On Tue, 2003-12-02 at 16:43, [EMAIL PROTECTED] wrote:
I am using gtk+ 2.2.4, so it should be the last stable
release. Every time when i use any GString / function i get leakage.
Then try to make a small test case for bugzilla.
I would be interested to see such as test case.
I've been
On Tue, 02 Dec 2003 19:06:44 -0700
Michael Torrie [EMAIL PROTECTED] wrote:
I've been using GString extensively in a non-gui project of mine and
have absolutely no leakage whatsoever. That's even running the main
loop over and over millions of times. I'm almost certain there's a
problem with
I hate and detest memory leaks. This is the main reason why I moved
away from microsoft system computers. They are notorious for memory
leaks and causing your system to crash, in fact this is probably one of
the main reasons why there computers crash so much. They must write
very bad