, and there are several posts about
memory leaks in gtkmm/gtk+. However, I am not clear as to what the
recommendation is. I am using gtkmm30 on fedora 18 x86 32-bit.
I built and ran a standard piece of sample code:
#include gtkmm.h
int main(int argc, char *argv[])
{
Glib::RefPtrGtk::Application app =
Gtk
I have searched through the past year, and there are several posts about
memory leaks in gtkmm/gtk+. However, I am not clear as to what the
recommendation is. I am using gtkmm30 on fedora 18 x86 32-bit.
I built and ran a standard piece of sample code:
#include gtkmm.h
int main(int argc, char
the past year, and there are several posts about
memory leaks in gtkmm/gtk+. However, I am not clear as to what the
recommendation is. I am using gtkmm30 on fedora 18 x86 32-bit.
I built and ran a standard piece of sample code:
#include gtkmm.h
int main(int argc, char *argv[])
{
Glib
I think the problem is in the use of g_markup_printf_escaped, this function
return a gchar* that you must free with g_free().
Probably you may take a look to ustring::compose functions.
Greetings
jamf.
--
Atentamente:
Juan Ángel Moreno Fernández
--
Proyecto Gelide
Could someone please tell how why these codes give me memory leaks.
//this class is a child of Gtk::Button
std::string display_text = some\ntext;
lb = new Gtk::Label();
lb-set_markup(g_markup_printf_escaped(span font='10.2'
font_family='%s'%s/span,FONT_FAMILY,u_space_to_newline
Dear Marcel!
ImageWindow::ImageWindow(string imagepath){
Glib::RefPtrGnome::Glade::Xml Widgetstree =
Gnome::Glade::Xml::create(interface2.glade);
Widgetstree-get_widget(imagewindow, imagewindow);
Widgetstree-get_widget(image, image);
The Tutorial at
Dear Marcel!
I have memory leaks with use of images...
Glib::RefPtrGdk::Pixbuf interfaceimage;
Image* workimage;
Gtk::Image *image;
interfaceimage = Gdk::Pixbuf::create_from_file(imagepath);
workimage=pixbuftoImage(interfaceimage
Agree with Mark Roberts very much.
On Mon, May 25, 2009 at 6:49 PM, Mark Roberts gt...@manumark.de wrote:
Dear Marcel!
I have memory leaks with use of images...
Glib::RefPtrGdk::Pixbuf interfaceimage;
Image* workimage;
Gtk::Image *image
that manual
memory management is better for me. Exist one way to do this, without
RefPtr?
Thanks again!
2009/5/25 Allen allenf...@gmail.com
Agree with Mark Roberts very much.
On Mon, May 25, 2009 at 6:49 PM, Mark Roberts gt...@manumark.de wrote:
Dear Marcel!
I have memory leaks with use
I have memory leaks with use of images...
I think that is pixbufs
I use pixbufs, loading like this:
Glib::RefPtrGdk::Pixbuf interfaceimage;
Image* workimage;
Gtk::Image *image;
interfaceimage = Gdk::Pixbuf::create_from_file(imagepath);
workimage
bug.
Maybe you could even investigate and maybe provide a patch.
I have tested the problem with plain glib and it happens there, too.
For now, I have created a glib bug report:
Bug 530054 – memory leaks in goption when using an array
We should test this again after the glib is fixed.
Cheers
.
Please do add the test case and valgrind errors to a bugzilla bug.
Maybe you could even investigate and maybe provide a patch.
I have tested the problem with plain glib and it happens there, too.
For now, I have created a glib bug report:
Bug 530054 – memory leaks in goption when
Hi,
I'm trying to see how to use the Glib::OpenEntry.
When I compile and run the attached program, valgrind complains on memory
leaks when I use OptionGroup::add_entry (const OptionEntry entry,
vecustrings arg).
Is this a real leak?
$ valgrind --leak-check=full options -b -s xxx -v aaa
On Thu, 2008-04-24 at 19:50 +0300, Ionutz Borcoman wrote:
Hi,
I'm trying to see how to use the Glib::OpenEntry.
When I compile and run the attached program, valgrind complains on memory
leaks when I use OptionGroup::add_entry (const OptionEntry entry,
vecustrings arg).
Is this a real
Correct, my mistake. Here it is:
$ pkg-config glibmm-2.4 --modversion
2.16.2
On Thursday 24 April 2008 10:25:43 pm Murray Cumming wrote:
On Thu, 2008-04-24 at 20:57 +0300, Ionutz Borcoman wrote:
I'm using the gtkmm from the Debian unstable:
$ pkg-config gtkmm-2.4 --modversion
2.12.7
On Thu, 2008-04-24 at 22:47 +0300, Ionutz Borcoman wrote:
Correct, my mistake. Here it is:
$ pkg-config glibmm-2.4 --modversion
2.16.2
That is the most recent one.
Please do add the test case and valgrind errors to a bugzilla bug.
Maybe you could even investigate and maybe provide a patch.
Here it is :
http://bugzilla.gnome.org/show_bug.cgi?id=383340
Paul, thank you again for the tips. I will follow your advice until
the above has been fixed.
regards,
Christopher Raine
On Dec 7, 2006, at 8:57 AM, Murray Cumming wrote:
On Wed, 2006-12-06 at 19:12 -0600, Paul Davis wrote:
- Original Message
From: Paul Davis [EMAIL PROTECTED]
To: Trigve Siver [EMAIL PROTECTED]
Sent: Tuesday, December 5, 2006 5:57:10 PM
Subject: Re: memory leaks
On 12/5/06, Trigve Siver [EMAIL PROTECTED] wrote:
Thanks for reply
I'm using this program:
#include gtkmm.h
int main(int argc, char
I am sorry that I cannot reply to the thread created by Trigve Siver
directly, I have just joined the mailing list.
I am currently evaluating gtkmm for use in our current project and
have encountered the same memory leaks Trigve Siver has reported
under WinXP/VS2005, latest gtkmm stable
currently evaluating gtkmm for use in our current project and
have encountered the same memory leaks Trigve Siver has reported
under WinXP/VS2005, latest gtkmm stable release. From my expierience,
the memory leaks reported by the crt-debugging functions are valid.
Considering the application
Siver
directly, I have just joined the mailing list.
I am currently evaluating gtkmm for use in our current project and
have encountered the same memory leaks Trigve Siver has reported
under WinXP/VS2005, latest gtkmm stable release. From my expierience,
the memory leaks reported by the crt
to the thread created by Trigve Siver
directly, I have just joined the mailing list.
I am currently evaluating gtkmm for use in our current project and
have encountered the same memory leaks Trigve Siver has reported
under WinXP/VS2005, latest gtkmm stable release. From my expierience
On Wed, 2006-12-06 at 19:12 -0600, Paul Davis wrote:
Well, two things. First off, hopefully someone more knowledgeable
(Where's Murray?)
If someone puts a test case in bugzilla, with clear instructions about
how they are observing a leak, we can investigate.
I'd be very surprised if gtkmm
Hi,
I don't know if this is the right mailing list but...I'm using gtkmm 2.10.5-1
on windows XP (installed from gtkmm-win32-devel-2.10.5-1.exe ) and when running
the simple program from tutorial (only one Gtk::Window and then run) I've got
18 memory leaks...I have tried the same program
Trigve,
Which example is it?
What are you using to detect memory leaks?
Chances are, they aren't real memory leaks, they're just being
reported as such because memory isn't explicity deallocated at the end
of the program which can happen for a number of reasons.
Paul
On 12/5/06, Trigve Siver
real memory leaks, they're just being
//reported as such because memory isn't explicity deallocated at the end
//of the program which can happen for a number of reasons.
I was thinking that something like this coudl be doing it.
thanks
Trigve
- Original Message
From: Paul Davis [EMAIL
26 matches
Mail list logo
