GNOME.org
 

[gtkmm] Gtkmm-forge digest, Vol 1 #449 - 7 msgs

Send Gtkmm-forge mailing list submissions to
	gtkmm-forge lists sourceforge net

To subscribe or unsubscribe via the World Wide Web, visit
	https://lists.sourceforge.net/lists/listinfo/gtkmm-forge
or, via email, send a message with subject or body 'help' to
	gtkmm-forge-request lists sourceforge net

You can reach the person managing the list at
	gtkmm-forge-admin lists sourceforge net

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Gtkmm-forge digest..."


gtkmm-forge is the mailing list that receives gtkmm bug reports from bugzilla.  A daily digest is sent to gtkmm-main, to encourage people to help fixing the bugs.


Today's Topics:

   1. [Bug 114568] Changed - Memory leak in Dialog::get_vbox() and get_action_area () (bugzilla-daemon widget gnome org)
   2. [Bug 114568] Changed - Memory leak in Dialog::get_vbox() and get_action_area () (bugzilla-daemon widget gnome org)
   3. [Bug 114568] Changed - Memory leak in Dialog::get_vbox() and get_action_area () (bugzilla-daemon widget gnome org)
   4. [Bug 116103] New - Many methods want zero value but there c++ reference parameter (bugzilla-daemon widget gnome org)
   5. [Bug 114568] Changed - Memory leak in Dialog::get_vbox() and get_action_area () (bugzilla-daemon widget gnome org)
   6. [Bug 114568] Changed - Memory leak in Dialog::get_vbox() and get_action_area () (bugzilla-daemon widget gnome org)
   7. [Bug 114568] Changed - Memory leak in Dialog::get_vbox() and get_action_area () (bugzilla-daemon widget gnome org)

--__--__--

Message: 1
From: bugzilla-daemon widget gnome org
To: gtkmm-forge lists sourceforge net,
	harald hopfes hopfes sysde eads net
Cc: 
Date: Fri, 27 Jun 2003 02:21:29 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 114568] Changed - Memory leak in Dialog::get_vbox() and get_action_area ()

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

http://bugzilla.gnome.org/show_bug.cgi?id=114568

Changed by murrayc usa net 

--- shadow/114568	Thu Jun 26 16:42:36 2003
+++ shadow/114568.tmp.23088	Fri Jun 27 02:21:29 2003
@@ -11,13 +11,13 @@
 AssignedTo: gtkmm-forge lists sourceforge net                            
 ReportedBy: harald hopfes hopfes sysde eads net               
 TargetMilestone: ---
 URL: 
 Cc: murrayc usa net
 Summary: Memory leak in Dialog::get_vbox() and get_action_area ()
-BugsThisDependsOn: 116014
+BugsThisDependsOn: 116014[NOTABUG]
 
 The following program causes memory leaks on each dialog open/close.
 The valgrind leak-check for one open/close and 10 open/close is appended 
 below.
 
 If you do a diff on both valgrind outputs, you can see that



--__--__--

Message: 2
From: bugzilla-daemon widget gnome org
To: gtkmm-forge lists sourceforge net,
	harald hopfes hopfes sysde eads net
Cc: 
Date: Fri, 27 Jun 2003 02:25:21 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 114568] Changed - Memory leak in Dialog::get_vbox() and get_action_area ()

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

http://bugzilla.gnome.org/show_bug.cgi?id=114568

Changed by murrayc usa net 

--- shadow/114568	Fri Jun 27 02:21:29 2003
+++ shadow/114568.tmp.24516	Fri Jun 27 02:25:21 2003
@@ -1564,6 +1564,19 @@
 gtk_button_new
 - on_object_qdata_destroyed is NOT called and no memory leak (???)
 
 gtk_vbox_new
 - on_object_qdata_destroyed is NOT called and memory leak (!!!)
 
+
+------- Additional Comments From murrayc usa net  2003-06-27 02:25 -------
+I am playing with using the "destroy" signal for GtkObjects (It does 
+not exist in GObjects, but I think we don't have the problem there). 
+It needs a little more work, because we need to check whether the 
+object is a GtkObject, or if it has the "destroy" signal, before 
+connecting that signal.
+
+The last bits of data that seem to be leaked might be explained by 
+this:
+http://www.gtk.org/faq/#AEN663
+But in general, it would be best now to wait for me to complete the 
+fix. Thanks for your help.



--__--__--

Message: 3
From: bugzilla-daemon widget gnome org
To: gtkmm-forge lists sourceforge net,
	harald hopfes hopfes sysde eads net
Cc: murrayc usa net
Date: Fri, 27 Jun 2003 04:31:01 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 114568] Changed - Memory leak in Dialog::get_vbox() and get_action_area ()

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

http://bugzilla.gnome.org/show_bug.cgi?id=114568

Changed by harald bugzilla gnome org hopfes de 

--- shadow/114568	Fri Jun 27 02:25:21 2003
+++ shadow/114568.tmp.5017	Fri Jun 27 04:31:01 2003
@@ -1577,6 +1577,20 @@
 
 The last bits of data that seem to be leaked might be explained by 
 this:
 http://www.gtk.org/faq/#AEN663
 But in general, it would be best now to wait for me to complete the 
 fix. Thanks for your help.
+
+------- Additional Comments From harald bugzilla gnome org hopfes de  2003-06-27 04:31 -------
+As the GtkVBox is part of the GtkDialog, it should not be floating
+anymore. (I will verify that). So I assume, the Dialog does a
+- gtk_vbox_new 
+- g_object_ref
+- (g_object_sink)
+- g_object_unref
+- gtk_widget_destroy
+
+And the qdata callback should be executed, right?
+It is only not executed, if some other thing did a g_object_ref on it,
+right?
+So who did it?



--__--__--

Message: 4
From: bugzilla-daemon widget gnome org
To: gtkmm-forge lists sourceforge net
Cc: 
Date: Fri, 27 Jun 2003 08:13:56 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 116103] New - Many methods want zero value but there c++ reference parameter

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

http://bugzilla.gnome.org/show_bug.cgi?id=116103

Changed by fuxx mail ru 

--- shadow/116103	Fri Jun 27 08:13:56 2003
+++ shadow/116103.tmp.29967	Fri Jun 27 08:13:56 2003
@@ -0,0 +1,35 @@
+Bug#: 116103
+Product: gtkmm
+Version: unspecified
+OS: All
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: normal
+Priority: Normal
+Component: general
+AssignedTo: gtkmm-forge lists sourceforge net                            
+ReportedBy: fuxx mail ru               
+TargetMilestone: ---
+URL: 
+Summary: Many methods want zero value but there c++ reference parameter
+
+As i said earlier in mailing list many methods want zero values, but we
+cannot pass
+it to them because c++ reference cannot be zero. And that methods do not
+have overloaded
+variant without that parameter.
+
+For instance Gtk::Widget::modify_bg has color parameter which if set to
+zero undoes
+modifications to original state.
+
+Other example was post to mailing list: Gtk::TreeView::set_cursor.
+
+And there are many such examples.
+
+I suggest we should modify m4 macros _WRAP_METHOD to allow it to generate
+several
+overloaded variants of same GTK+ function where it can get 0 value as
+parameter,
+or any other way for programmer to control this process.



--__--__--

Message: 5
From: bugzilla-daemon widget gnome org
To: gtkmm-forge lists sourceforge net,
	harald hopfes hopfes sysde eads net
Cc: 
Date: Fri, 27 Jun 2003 11:55:16 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 114568] Changed - Memory leak in Dialog::get_vbox() and get_action_area ()

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

http://bugzilla.gnome.org/show_bug.cgi?id=114568

Changed by murrayc usa net 

--- shadow/114568	Fri Jun 27 11:33:58 2003
+++ shadow/114568.tmp.5086	Fri Jun 27 11:55:15 2003
@@ -1619,6 +1619,14 @@
 
 I think that would be the cleanest way.
 
 After all: Sorry that I was writing hundreds of comments and opening 
 an unneccessary BugReport in GTK+.
 
+
+------- Additional Comments From murrayc usa net  2003-06-27 11:55 -------
+Hmm, that is not the solution that I expect. Can you confirm it by
+a) Verifying it by using the debug output - that should show every 
+ref and unref and other lifecycle calls.
+b) Verifying that it is a problem by modifying the C test case to do 
+the same things.
+?



--__--__--

Message: 6
From: bugzilla-daemon widget gnome org
To: gtkmm-forge lists sourceforge net,
	harald hopfes hopfes sysde eads net
Cc: murrayc usa net
Date: Fri, 27 Jun 2003 11:33:58 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 114568] Changed - Memory leak in Dialog::get_vbox() and get_action_area ()

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

http://bugzilla.gnome.org/show_bug.cgi?id=114568

Changed by harald hopfes hopfes sysde eads net 

--- shadow/114568	Fri Jun 27 04:31:01 2003
+++ shadow/114568.tmp.26385	Fri Jun 27 11:33:58 2003
@@ -1591,6 +1591,34 @@
 - gtk_widget_destroy
 
 And the qdata callback should be executed, right?
 It is only not executed, if some other thing did a g_object_ref on it,
 right?
 So who did it?
+
+------- Additional Comments From harald hopfes hopfes sysde eads net  2003-06-27 11:33 -------
+Murray:
+
+I think the key to the problem is the else part inside 
+ Object::_init_unmanage
+
+because it does a
+
+  g_object_ref on that GtkVBox
+
+which is never ever unref'd. And that is the reason for not calling 
+the qdata callback.
+
+I would say, either the g_object_ref needs to be removed or there 
+must be some kind of 2-stage destroy process in gtkmm also
+
+Something like that:
+
+- leave the g_object_ref inside Object::_init_unmanage as it is
+- Add a g_signal_connect("destroy") for a new method that does
+  a g_object_unref
+
+I think that would be the cleanest way.
+
+After all: Sorry that I was writing hundreds of comments and opening 
+an unneccessary BugReport in GTK+.
+



--__--__--

Message: 7
From: bugzilla-daemon widget gnome org
To: gtkmm-forge lists sourceforge net,
	harald hopfes hopfes sysde eads net
Cc: murrayc usa net
Date: Fri, 27 Jun 2003 12:06:29 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 114568] Changed - Memory leak in Dialog::get_vbox() and get_action_area ()

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

http://bugzilla.gnome.org/show_bug.cgi?id=114568

Changed by harald hopfes hopfes sysde eads net 

--- shadow/114568	Fri Jun 27 11:55:15 2003
+++ shadow/114568.tmp.10391	Fri Jun 27 12:06:28 2003
@@ -1627,6 +1627,9 @@
 Hmm, that is not the solution that I expect. Can you confirm it by
 a) Verifying it by using the debug output - that should show every 
 ref and unref and other lifecycle calls.
 b) Verifying that it is a problem by modifying the C test case to do 
 the same things.
 ?
+
+------- Additional Comments From harald hopfes hopfes sysde eads net  2003-06-27 12:06 -------
+Murray: Forget it, it (2 stage destroy) did not work.




--__--__--

_______________________________________________
Gtkmm-forge mailing list
Gtkmm-forge lists sourceforge net
https://lists.sourceforge.net/lists/listinfo/gtkmm-forge


End of Gtkmm-forge Digest
[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]