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=78241 --- shadow/78241 2006-05-02 11:42:31.000000000 -0400 +++ shadow/78241.tmp.4254 2006-05-03 05:40:17.000000000 -0400 @@ -283,6 +283,31 @@ ------- Additional Comments From [EMAIL PROTECTED] 2006-05-02 11:42 ------- Created an attachment (id=16896) Hps log (when mod_mono_server crash) + +------- Additional Comments From [EMAIL PROTECTED] 2006-05-03 05:40 ------- +if is enabled +you get this (with my program which create processes) + +** Message: _wapi_handle_ref: Process handle 0x516 ref now 2 +Started 269 +** Message: _wapi_handle_ref: Thread handle 0x400 ref now 292 +** Message: : Closing process 0x50eb0, handle 0x516 +** Message: _wapi_handle_unref: Process handle 0x516 ref now 1 +(destroy FALSE) +Killed + +why destroy always=FALSE; +I've seen this in handle.c : + +/* Possible race condition here if another thread refs the + * handle between here and setting the type to UNUSED. I + * could lock a mutex, but I'm not sure that allowing a handle + * reference to reach 0 isn't an application bug anyway. + */ + destroy = (InterlockedDecrement (&_WAPI_PRIVATE_HANDLES(idx).ref) ==0); + +is there a bug here? + _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
