push coming. I learned the lesson the hard way long ago to never ever hold
a lock when issuing a call to unknown code. This ended up biting us as some
work was being done on the callback and the accepting of a new request was
being blocked :( I might have 2-3 more as I try to figure out the
bottlen
I believe the problem only exists in send async.
We have re-applied patch locally and it brings us back to stable.
On Sat, Dec 1, 2012 at 1:32 PM, Roope Kangas wrote:
> Hi guys. I dont know the history of this but. Since we are developing a
> mmo game on mono...
>
> Whats the situation? Is ther
We have code that shows the issue
https://github.com/ysw/mono-socket-problem/tree/master/SocketTest
Greg
On Fri, Nov 30, 2012 at 4:10 PM, Rodrigo Kumpera wrote:
> Btw, I managed to find a linux bot that shows the io callback issue.
> The TP test works fine though.
>
>
> On Fri, Nov 30, 2012 at
Actually, scratch my comment. There are two locks in there. Look more
carefully at the change...
Sadly the bug that it says to fix is private so one cannot extract a
regression/stress test from it.
On 06/12/12 08:08, Greg Young wrote:
push coming. I learned the lesson the hard way long ag
Hi,
We sometimes get runtime crashes during the application run and it seems
that it happens inside JIT compiler. The crash is not happening constantly,
just once in a few runs.
We run under Mono 3.0.1 (no/301b6c6 Tue Dec 4 15:13:23 EET 2012) with SGen.
Here is the stack trace:
Thread 5 (Threa
Please file a bug report with a reproducible test case.
On Thu, Dec 6, 2012 at 10:44 AM, Andrii Nakryiko
wrote:
> Hi,
>
> We sometimes get runtime crashes during the application run and it seems
> that it happens inside JIT compiler. The crash is not happening constantly,
> just once in a few ru
Its not reproducible even in our code base. Sometimes we get a sigfault
sometimes not. It may happen 20 times in a row and not happen 20 times on
an identical box.
On Thu, Dec 6, 2012 at 6:13 PM, Rodrigo Kumpera wrote:
> Please file a bug report with a reproducible test case.
>
>
> On Thu, Dec 6
The method in question is EventStore.Transport.Tcp.TcpConnection:EnqueueSend,
you can check if calling it directly triggers the bug.
On Thu, Dec 6, 2012 at 11:20 AM, Greg Young wrote:
> Its not reproducible even in our code base. Sometimes we get a sigfault
> sometimes not. It may happen 20 tim
It's not about that particular method, we got earlier same kind of crashes
on different methods, for
instance, ProtoBuf.Serializers.ArrayDecorator:Write ()
If I remember correctly, I got this crash even for some method on List,
though I can't locate that log quickly. If I get it, will post here.
Al
On Thu, Dec 6, 2012 at 12:38 PM, Andrii Nakryiko
wrote:
> It's not about that particular method, we got earlier same kind of crashes
> on different methods, for
> instance, ProtoBuf.Serializers.ArrayDecorator:Write ()
> If I remember correctly, I got this crash even for some method on List,
> thou
Hi,
Currently I am obtaining the MonoClass* objects via mono_class_from_name
which acts upon the MonoImage of provided assembly.
However, I am planning my project to span throughout few assemblies and I
still want the native host to be able to load classes by name. Do I have to
track the loaded a
11 matches
Mail list logo
