This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(256, 0%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EH%3C/text%3E%3C/svg%3E)
I have been chasing a strange occasional IndexOutOfRangeException for a while and pinned it on the following line:
myQueue.Enqueue(myObject)
where:
protected Queue<MyObject> myQueue{ get; set; }
I don't know how this is possible. The stack trace:
System.IndexOutOfRangeException: Index was outside the bounds of the array.
Stack Trace:
at Internal.Runtime.CompilerHelpers.ThrowHelpers.ThrowIndexOutOfRangeException() + 0x25
at ClassLibraryFoo.NVT.DecoderWin.<MethodFoo>d__38.MoveNext() + 0x46f
Could anyone shed some light on this?
The stack seems to be related to an issue with DecoderWin.
Maybe you are using parallel threads incorrectly.
Thank you, Viorel. Yes, myQueue is accessed by multiple threads. Did you mean that this is a threading issue, not related to the index or size of myQueue?
Thank you for the tip. I will definitely give Queue.Synchronized a shot. I used ConcurentQueue for many years until recently and changed it to Queue because I suspected ConcurentQueue was leaking memory as reported by some others.
Now, I have further indisputable proof that myQueue.Enqueue(myObject) throws the IndexOutOfRangeException with the following code to catch the exception:
try
{
myQueue.Enqueue(myObject);
}
catch (Exception ex)
{
//log
}
I will try Queue.Synchronized(myQueue) to see if it fixes it.
Hi @Hong ,
Haven't heard from you for a while. can Queue.Synchronized(myQueue) fix the problem?
@Junjie Zhu - MSFT I released an update with the use of Queue.Synchronized(myQueue) yesterday. I have not seen the IndexOutOfRangeException from this update, so I assume it has fixed the problem. The comment from Viorel can be turned into the answer.
Hi @Hong ,
Glad to hear that, I turned the correct solution into an answer, to help more people who encounter the same problem, If the answer is the right solution, please click "Accept Answer" and kindly upvote it.
I think that the exception is caused by threading issues.
Maybe you can use a mutex, or a ConcurentQueue, or a queue returned by Queue.Synchronized(myQueue).
Also see the remark about the enumerators: