Closed GoogleCodeExporter closed 9 years ago
woooo, what a professional report! Thanks.
Original comment by freezing...@gmail.com
on 18 Jul 2008 at 5:30
Already fixed, just check out r371 or the latest version.
Original comment by freezing...@gmail.com
on 19 Jul 2008 at 3:57
Great! Thanks for your quick response.
Original comment by ignacioa...@gmail.com
on 19 Jul 2008 at 2:44
Hi! I realized that you reverted the modification you've made. Microsoft's
documentation states that:
"Enumerating through a collection is intrinsically not a thread-safe procedure.
Even
when a collection is synchronized, other threads can still modify the
collection,
which causes the enumerator to throw an exception. To guarantee thread safety
during
enumeration, you can either lock the collection during the entire enumeration or
catch the exceptions resulting from changes made by other threads."
So, even in the case you use ArrayList.Synchronized, you should add locks when
iterating over a collection to avoid getting an exception that says that the
collection had been modified during the iteration.
Original comment by ignacioa...@gmail.com
on 21 Jul 2008 at 7:44
Ok, fixed.
Original comment by hepha...@gmail.com
on 22 Jul 2008 at 12:30
Original comment by hepha...@gmail.com
on 23 Jan 2009 at 5:40
Original issue reported on code.google.com by
ignacioa...@gmail.com
on 17 Jul 2008 at 8:38Attachments: