[Mono-bugs] [Bug 49993][Cos] New - Possible leak in mono_class_proxy_vtable

[bugzilla-daemon@bugzilla.ximian.com]

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.

Changed by gonzalo@ximian.com.

http://bugzilla.ximian.com/show_bug.cgi?id=49993

--- shadow/49993	2003-10-22 08:08:17.000000000 -0400
+++ shadow/49993.tmp.13421	2003-10-22 08:08:17.000000000 -0400
@@ -0,0 +1,29 @@
+Bug#: 49993
+Product: Mono/Runtime
+Version: unspecified
+OS: All
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Cosmetic
+Component: misc
+AssignedTo: mono-bugs@ximian.com                            
+ReportedBy: gonzalo@ximian.com               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: Possible leak in mono_class_proxy_vtable
+
+See metadata/object.c.
+
+The function mono_class_proxy_vtable allocates memory for the vtable and
+interface offsets from the domain mempool (does
+arch_create_remoting_trampoline allocate memory too?).
+
+After that, in the case when "/* Somebody got in before us */", the virtual
+table is freed using g_free (it comes from a mono_mem_pool_alloc) and the
+interface_offsets are not freed.
+
+This is unlikely to happen, but, well...