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=75119 --- shadow/75119 2005-06-02 17:31:32.000000000 -0400 +++ shadow/75119.tmp.28781 2005-06-08 12:12:57.000000000 -0400 @@ -10,13 +10,12 @@ Component: GC AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] QAContact: [EMAIL PROTECTED] TargetMilestone: --- URL: -Cc: Summary: thread/gc issue ... So - I think I ommitted to file this as a bug before - however; it's rather important for Mono/OO.o OO.o is highly threaded, and we can't be compiling it with some funky gc @@ -65,6 +64,18 @@ de-register thread stacks on destruction; surely. hmm. ------- Additional Comments From [EMAIL PROTECTED] 2005-06-02 17:31 ------- Also, could the 'mono_gc_ensure_registered' function be called 'mono_gc_register_thread' instead ? + +------- Additional Comments From [EMAIL PROTECTED] 2005-06-08 12:12 ------- +New patch with Zoltan's re-name, of course - this is not the world's +most elegant patch as discussed; it is OTOH critical for the OO.o/Mono +bridge. + +I have tried to update this so it'll free any foreign thread data on +thread exit - which should help improve the situation. Unfortunately - +it's rather tricky to test. Perhaps you have some mixed C / Mono +test-apps that it'd be easy to hook that into (?). + +Anyhow - HTH. _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
