You can try to run mono without inlining: `mono -O=-inline [...]'
From: mono-list-boun...@lists.ximian.com
on behalf of Alan
Sent: Tuesday, June 21, 2016 2:33 AM
To: Алексей Богомолов
Cc: Mono List
Just realized I forgot one possibly important point. All I/O is now being done
in /dev/shm (tmpfs) so any clustered file system load/performance issues should
not affect the code.
Cheers.
From:
>
on
Hi Rodrigo,
I finally can semi-reliably (most of the time) reproduce these hung processes.
The strace, gdb backtrace, and CUE cards for a single hung mono instance is
shown below.
1. I am now running on mono-4.4.0. The hanging issue still exists.
2. The code is compiled in VS 2015 and
This happens on .NET too. This gives a good description of what's happening
and why.
http://www.hanselman.com/blog/ReleaseISNOTDebug64bitOptimizationsAndCMethodInliningInReleaseBuildCallStacks.aspx
Alan
On 21 June 2016 at 09:31, Алексей Богомолов wrote:
> This behavior
This behavior makes difficult to troubleshoot errors, especially in
external libraries. Example code:
public class ExceptionReThrow{
public void Test(){
try
{
M1 ();
}
catch (Exception ex)
{
Console.WriteLine(ex);
}
}