[Mono-bugs] [Bug 74828][Blo] Changed - race in MonoEnumInfo
bugzilla-daemon@bugzilla.ximian.com
bugzilla-daemon@bugzilla.ximian.com
Wed, 4 May 2005 20:25:34 -0400 (EDT)
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 miguel@ximian.com.
http://bugzilla.ximian.com/show_bug.cgi?id=74828
--- shadow/74828 2005-05-04 20:16:53.000000000 -0400
+++ shadow/74828.tmp.19158 2005-05-04 20:25:34.000000000 -0400
@@ -3,19 +3,20 @@
Version: 1.1
OS: unknown
OS Details:
Status: NEW
Resolution:
Severity: Unknown
-Priority: Normal
+Priority: Blocker
Component: CORLIB
-AssignedTo: mono-bugs@ximian.com
+AssignedTo: lupus@ximian.com
ReportedBy: james@ximian.com
QAContact: mono-bugs@ximian.com
TargetMilestone: ---
URL:
+Cc: lluis@ximian.com,naresh@novell.com
Summary: race in MonoEnumInfo
Got the following trace today, indicating a race condition in sychronized
hashtables I think. It does not seem to be very frequent.
System.ArgumentException: Key duplication when adding:
@@ -41,6 +42,12 @@
Novell.Zenworks.Zmd.Public.UnixClientTransportSink:ProcessMessage (IMessage
msg, ITransportHeaders requestHeaders, System.IO.Stream requestStream,
ITransportHeaders responseHeaders, System.IO.Stream responseStream)
in <0x0024b>
System.Runtime.Remoting.Channels.BinaryClientFormatterSink:SyncProcessMessage
(IMessage msg)
+
+------- Additional Comments From miguel@ximian.com 2005-05-04 20:25 -------
+I do not think it has to do with Synchornized hashtables, because we
+take a lock before getting into that code
+
+Assigning to Paolo, CCing Lluis