Hi, On 3/30/07, Alan McGovern <[EMAIL PROTECTED]> wrote: > That leaves me with the question of how the hell a SocketAsyncResult is 10 > megs in size!
It's not the SocketAsyncResult itself that's 10 megs in size, it's the object array that holds them that is 10 megs in size. > I'm going to do a bit of profiling to count how many socket BeginXXX calls > are made from my own code as compared to the EndXXX calls to see how they > match up. I think this is a good idea, and if that doesn't work out, I would use Mono's tracing facility to see how often the methods I mentioned in my last email were being called and in what order. And if that doesn't work, instrument the class libs themselves. > I can verify that the exact same code running under Mono 1.2 and earlier > does *not* exhibit the same behavior, everything works fine. I only came > across this bug after updating my mono installation to 1.2.3. This is why i > think it's a mono bug, however i can't reproduce the problem in the form of > an NUnit test. It's probably in the sockets code, so take a diff of System.Net.Sockets.Socket between 1.2 and 1.2.3 and see what, if anything changed. If you can narrow it down to a specific change between the releases, that will hopefully make it easier to write a test case. Joe _______________________________________________ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list