[Mono-bugs] [Bug 77943][Nor] New - double-free crash during some unit tests and on app exit

[bugzilla-daemon at 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 matt at use.net.

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

--- shadow/77943	2006-03-28 23:38:38.000000000 -0500
+++ shadow/77943.tmp.11969	2006-03-28 23:38:38.000000000 -0500
@@ -0,0 +1,61 @@
+Bug#: 77943
+Product: Mono: Class Libraries
+Version: 1.1
+OS: 
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Normal
+Component: libgdiplus
+AssignedTo: peter at novonyx.com                            
+ReportedBy: matt at use.net               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: double-free crash during some unit tests and on app exit
+
+Description of Problem:
+When running the SWF unit tests, or running WinForms apps and exiting them,
+glibc detects a double-free or corruption. With latest SVN head as of
+3/28/2006 @ 8:15PM PST.
+
+Actual Results:
+*** glibc detected *** double free or corruption (!prev):
+0x0000000000ba9ac0 ***
+
+Program received signal SIGABRT, Aborted.
+[Switching to Thread 32771 (LWP 12533)]
+0x00002aaaab5d3ad9 in kill () from /lib/libc.so.6
+(gdb) bt
+#0  0x00002aaaab5d3ad9 in kill () from /lib/libc.so.6
+#1  0x00002aaaab178841 in pthread_kill (thread=12533, signo=6) at signals.c:69
+#2  0x00002aaaab178bc2 in __pthread_raise (sig=6) at signals.c:200
+#3  0x00002aaaab5d37d2 in raise () from /lib/libc.so.6
+#4  0x00002aaaab5d4b12 in abort () from /lib/libc.so.6
+#5  0x00002aaaab606cd7 in __fsetlocking () from /lib/libc.so.6
+#6  0x00002aaaab60bba0 in malloc_usable_size () from /lib/libc.so.6
+#7  0x00002aaaab60c70a in free () from /lib/libc.so.6
+#8  0x00002aaaacf98575 in gdip_bitmap_dispose (bitmap=0xe8a2d0) at bitmap.c:150
+#9  0x00002aaaacfaf385 in GdipDisposeImage (image=0xe8a2d0) at image.c:125
+#10 0x00000000400b0835 in ?? ()
+#11 0x000000004001b23b in ?? ()
+#12 0x000000000073e370 in ?? ()
+#13 0x000000000073e340 in ?? ()
+#14 0x0000000000dcce60 in ?? ()
+#15 0x00000000400b07cb in ?? ()
+#16 0x0000000000947b80 in ?? ()
+#17 0x00002aaaac504d50 in ?? ()
+#18 0x00002aaaac504c70 in ?? ()
+#19 0x00002aaaadf84a00 in ?? ()
+#20 0x000000000106d9b0 in ?? ()
+#21 0x0000000000000000 in ?? ()
+
+
+How often does this happen? 
+Pretty much every time the SWF unit tests are run, after the
+MonthCalendarTest fixture is run. When running that fixture by itself,
+everything is okay, though. This makes me think that it has to do with when
+things from previous tests are GC'd rather than anything that fixture
+specifically does.