[Mono-bugs] [Bug 76491][Maj] New - mono.exe gets hanged while working.

[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 francis at aspl.es.

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

--- shadow/76491	2005-10-20 13:10:02.000000000 -0400
+++ shadow/76491.tmp.18405	2005-10-20 13:10:02.000000000 -0400
@@ -0,0 +1,82 @@
+Bug#: 76491
+Product: Mono: Runtime
+Version: 1.1
+OS: 
+OS Details: Microsoft Windows XP SP2 (up to date)
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Major
+Component: JIT
+AssignedTo: lupus at ximian.com                            
+ReportedBy: francis at aspl.es               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: mono.exe gets hanged while working.
+
+Hi,
+
+The problem has been detected while using the Mono installation bundled 
+with the Mono Setup (1.1.9.2) for windows platforms.
+
+If you try to run any program with the jit, it gets hanged sometimes, 
+starting to consume CPU. It has no predictable method to be reproduced 
+the problem. But, once hanged, I've got a backtrace, using gdb, from the 
+thread I think could be the problem. This is the BT:
+
+
+(gdb) backtrace
+#0  0x100d6e9d in _libwsock32_a_iname ()
+#1  0x00faea48 in ?? ()
+#2  0x100d717a in _libwsock32_a_iname ()
+#3  0x100d832a in _libwsock32_a_iname ()
+#4  0x100d405e in _libwsock32_a_iname ()
+#5  0x1000f257 in g_io_channel_fill_buffer ()
+#6  0x10023919 in g_pattern_spec_new ()
+#7  0x100077a8 in g_date_get_day_of_year ()
+#8  0x100546ea in attr_data ()
+#9  0x00be0052 in ?? ()
+#10 0x01161dc2 in ?? ()
+#11 0x01161d3f in ?? ()
+#12 0x01160b99 in ?? ()
+#13 0x01161d14 in ?? ()
+#14 0x01161ce4 in ?? ()
+#15 0x011619ff in ?? ()
+#16 0x0116179d in ?? ()
+#17 0x0116128e in ?? ()
+#18 0x01161225 in ?? ()
+#19 0x0116082d in ?? ()
+#20 0x01160577 in ?? ()
+#21 0x0116008f in ?? ()
+#22 0x0115feab in ?? ()
+#23 0x01125afd in ?? ()
+#24 0x010b5fd4 in ?? ()
+#25 0x010b35c0 in ?? ()
+#26 0x010a18ac in ?? ()
+#27 0x100805cf in _bss_end__ ()
+#28 0x1008082c in _bss_end__ ()
+#29 0x10034fe6 in g_utf8_to_ucs4 ()
+#30 0x004012fa in ?? ()
+#31 0x00401236 in ?? ()
+#32 0x00401288 in ?? ()
+#33 0x7c816d4f in libgthread_2_0_0_dll_iname ()
+
+
+Other threads seems to be ok because they all have:
+
+(gdb) backtrace
+#0  0x7c91eb94 in libgthread_2_0_0_dll_iname ()
+#1  0x7c91e9ab in libgthread_2_0_0_dll_iname ()
+#2  0x7c809c86 in libgthread_2_0_0_dll_iname ()
+#3  0x791d25d5 in libgthread_2_0_0_dll_iname ()
+#4  0x791d254c in libgthread_2_0_0_dll_iname ()
+#5  0x7c80b50b in libgthread_2_0_0_dll_iname ()
+
+Which seems to be idle threads.
+
+I can confirm this problem was never detected using the Mono installation 
+1.1.7 for windows.
+
+Cheers.