I am using:
Mono JIT compiler version 2.10.11 (mono-2-10/2baeee2 Wed Jan 16 16:40:16 EST
2013)
Copyright (C) 2002-2012 Novell, Inc, Xamarin, Inc and Contributors.
www.mono-project.com
TLS: normal
SIGSEGV: normal
Notification: kqueue
Architecture: x86
Disabled: none
Misc:
Use a recent version of mono on OSX because DISABLE_AIO has no effect on
OSX since the kqueue backend has been disabled.
On Tue, Apr 23, 2013 at 3:46 AM, Roope Kangas wrote:
> Hi,
>
> On OSX I keep getting "shutting down finalizer thread timed out" or just
> process hang ups on exit if I do not
Hi,
On OSX I keep getting "shutting down finalizer thread timed out" or just
process hang ups on exit if I do not use MONO_DISABLE_AIO.
And only if I try to use async send so I don't think this is linux only...
--
Roope Kangas / LSD, Grand Cru
+358 40 869 6976 ro...@grandcrugames.com
h
Should this be the new default build for linux then?
On Tue, Apr 23, 2013 at 4:23 AM, Rodrigo Kumpera wrote:
> The problem is specific to the epoll backed, if you disable it[1] your
> problem is fixed.
> I could repro it on linux-amd64 with epoll enabled but could not with it
> disabled.
>
> The
The problem is specific to the epoll backed, if you disable it[1] your
problem is fixed.
I could repro it on linux-amd64 with epoll enabled but could not with it
disabled.
The way to fix this is:
-move locking to the epoll backend and make sure it works there;
-use a pipe like other backends to w
We also cannot use BeginSend atm. I suspect we have the same problem.
Whats the situation with mono TCP stack? From Xamarin point-of-view all
epoll,kqueue,tpoll work perfectly on all os?
Is there some wiki / html page that would have list of current limitations and
bugs? Do we have some common
We still have this patch that we use with mono.
diff --git a/mono/metadata/threadpool.c b/mono/metadata/threadpool.c
index e8a2f1a..f83e473 100644
--- a/mono/metadata/threadpool.c
+++ b/mono/metadata/threadpool.c
@@ -555,8 +555,8 @@ socket_io_add (MonoAsyncResult *ares,
MonoSocketAsyncResult *stat
