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 [EMAIL PROTECTED] http://bugzilla.ximian.com/show_bug.cgi?id=80743 --- shadow/80743 2007-03-29 18:14:06.000000000 -0500 +++ shadow/80743.tmp.16229 2007-04-04 14:15:21.000000000 -0400 @@ -559,6 +559,25 @@ /usr/local/bin/mono[0x80f58c4] /usr/local/bin/mono[0x8106142] /usr/local/bin/mono[0x8116da5] /lib/libpthread.so.0[0xd9e3db] /lib/libc.so.6(clone+0x5e)[0xcf826e] + +------- Additional Comments From [EMAIL PROTECTED] 2007-04-04 14:15 ------- +Disabling the domain unloading code makes the segfault go away when +using Gert's Tinyhost (this does not work with xsp, it hangs after the +first app restart): + +export MONO_NO_UNLOAD=1 +mono tinyhost.exe + +With that I've been able to change number of loop runs in tinyhost.exe +from 20 to 400 without seeing any crash at all. After 400 runs, my +system started crawling as all available memory was used up by "dead" +domains (and other leaked resources). + +So it looks very much like the problem is in the runtime, in the +domain unloading code (or code called by it). I know that code to be a +nasty thing and hard to get right. + +Is there anything I can do to help tracking down this bug? _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
