Hi,
I'm running the following .net program on mono (Ubuntu 12, sources
3.8.13.12)
and after ~1 minute where the memory rises up (without any reason according
to the code below), mono crash with TOO MANY HEAP SECTIONS.
(using Queue + lock is stable)
I got mono sources from Git and compile them with
I have to admit I am a bit surprised how buggy concurrentqueue is.
If you are reading this and building software that needs to run in a
stable fashion just say no to concurrent queue. I have placed a few
issues here before but we have seen it infinite loop internally, throw
null reference
I've also been having NPE's with ConcurrentQueue in the context of
TryDequeue with multiple threads. Was there a fix for this did it make
it into 2.11.3?
On Fri, Aug 10, 2012 at 5:28 AM, Greg Young gregoryyou...@gmail.com wrote:
I can't as I am about to head out of country (its also spuratic
We regularly can cause problems with ConcurrentQueue such as
System.NullReferenceException: Object reference not set to an instance
of an object
at
System.Collections.Concurrent.ConcurrentQueue`1[System.IO.FileStream].TryDequeue
(System.IO.FileStream result) [0x0] in filename unknown:0
Hey,
What version of Mono are you testing against?
Alan
On 10 August 2012 09:52, Greg Young gregoryyou...@gmail.com wrote:
We regularly can cause problems with ConcurrentQueue such as
System.NullReferenceException: Object reference not set to an instance
of an object
at
trunk.
On Fri, Aug 10, 2012 at 2:53 AM, Alan alan.mcgov...@gmail.com wrote:
Hey,
What version of Mono are you testing against?
Alan
On 10 August 2012 09:52, Greg Young gregoryyou...@gmail.com wrote:
We regularly can cause problems with ConcurrentQueue such as
Could you run you program in debug mode and paste the line number where the
problem happen?
--
Jérémie Laval
http://neteril.org
On Fri, Aug 10, 2012 at 10:53 AM, Greg Young gregoryyou...@gmail.comwrote:
trunk.
On Fri, Aug 10, 2012 at 2:53 AM, Alan alan.mcgov...@gmail.com wrote:
Hey,
I can't as I am about to head out of country (its also spuratic behaviour)
I believe @yuriy probably can though.
Cheers,
Greg
On Fri, Aug 10, 2012 at 5:26 AM, Jérémie Laval jeremie.la...@gmail.com wrote:
Could you run you program in debug mode and paste the line number where the
problem
