Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
GitHub or Developer Community with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
Created attachment 10506 [details]
Cannot transition thread 0xf43011b8 from RUNNING with FINISH_ASYNC_SUSPEND
at <unknown> <0xffffffff>
at (wrapper managed-to-native) System.Net.Sockets.Socket.Connect_internal (intptr,System.Net.SocketAddress,int&) <0xffffffff>
at System.Net.Sockets.Socket.Connect_internal (System.Net.Sockets.SafeSocketHandle,System.Net.SocketAddress,int&) <0x00033>
at System.Net.Sockets.Socket.Connect (System.Net.EndPoint) <0x000e7>
at System.Net.WebConnection.Connect (System.Net.HttpWebRequest) <0x0042f>
at System.Net.WebConnection.InitConnection (object) <0x0021b>
at System.Net.WebConnection.<WebConnection>m__0 (object) <0x00017>
at (wrapper runtime-invoke) <Module>.runtime_invoke_void__this___object (object,intptr,intptr,intptr) <0xffffffff>
Mono JIT compiler version 4.1.0 (master/a081090 Mi 25. Mär 23:19:27 CET 2015)
Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com
LLVM: supported, not enabled.
this is happens very often...
my tool is crashing in less then 10 min under usage :/
If you could upload a code sample which triggers this bug, it would make reproducing and fixing it much easier.
Unfortunately the backtrace in this case is not enough to have something to work with.
Please provide a test case that allow us to reproduce this behavior.
Created attachment 10813 [details]
Here's a test case.
Created attachment 10892 [details]
Looks like there needs to be some CPU load for this to occur, so here's another testcase. Please let me know if it doesn't work and I'll provide access to a test box where it can be reproduced.
Also seems to help if you run several instances at the same time, for example in while loop in screen.
Thanks for the updated test case, I'll give it a try this week and report back results.
I see the same issue when running the System testsuite on Linux (locally, on my CI and on Mono Jenkins). Although with a slightly different stacktrace:
> Cannot transition thread 0x2b9f780008e0 from RUNNING with FINISH_ASYNC_SUSPEND
> at <unknown> <0xffffffff>
> at (wrapper managed-to-native) System.Net.Sockets.Socket.Accept_internal (intptr,int&,bool) <IL 0x0000f, 0xffffffff>
> at System.Net.Sockets.Socket.Accept_internal (System.Net.Sockets.SafeSocketHandle,int&,bool) [0x00006] in /home/alexander/dev/mono/mcs/class/System/System.Net.Sockets/Socket.cs:1066
> at System.Net.Sockets.Socket.Accept () [0x00008] in /home/alexander/dev/mono/mcs/class/System/System.Net.Sockets/Socket.cs:893
> at System.Net.Sockets.TcpListener.AcceptSocket () [0x00016] in /home/alexander/dev/mono/mcs/class/System/System.Net.Sockets/TcpListener.cs:184
> at MonoTests.System.Net.SocketResponder.Listen () [0x00007] in /home/alexander/dev/mono/mcs/class/System/Test/System.Net/SocketResponder.cs:111
> at System.Threading.Thread.StartInternal () [0x00016] in /home/alexander/dev/mono/mcs/class/corlib/System.Threading/Thread.cs:694
> at (wrapper runtime-invoke) object.runtime_invoke_void__this__ (object,intptr,intptr,intptr) <IL 0x00056, 0xffffffff>
It reproduces 100% of the time (though sometimes the testsuite just deadlocks).
With the "Better(?) testcase" from Kari I can also repro the issue in a few seconds on a Mono built today.
Digging through my CI logs, this is happening since quite some time. The first time it happened with commit 0468321ad188 (but that commit only changes something for android, so it was likely introduced earlier). It then happens very rarely, up until https://github.com/mono/mono/pull/1691 was merged. From then on it happens 100% of the time.
A PR to fix the issue was just merged: