[Mono-devel-list] Web Socket Code
monoguy at speakeasy.net
Fri Jul 30 12:30:01 EDT 2004
Does this mean that the code in the message I was replying to from Colt
Majkrzak doesn't reproduce for you either? If the above mentioned code
sample also doesnt reproduce for you, I will try to make another minimal
testcase. I only notice this issue when I run the code for a very long
time (on the order of days), running it for a couple of hours always
works normally. IIRC my code worked for days rather than 12-14 hours
before dying with the same error in versions of mono from 6 months ago.
As far as the specifics go, the code in bugzilla is in fact using the
same method calls (socket.Receive) as my code. It is also functionally
Thanks for the reply, I'd really like to help in order to get this issue
Dick Porter wrote:
>On Fri, 2004-07-30 at 04:07, Tron Chambers wrote:
>>I have been seeing this exact issue as well.
>>I have very similar code that actually uses lower level libraries than
>>WebClient, as it reads from the socket directly. After about 12 hours
>>or so of reading and writing to sockets in a constant loop it dies with
>>a some sort of GC out of memory error (it's not neccesarily the same
>>one, but it is usually the RETURNING NIL one in the boehm library) and
>>it appears to be an infinite loop. (processor usage at 100% etc).
>>I have spent a great deal of time trying to understand this bug, but
>>have yet to nail down a smoking gun. I would guess it is a leak in
>>freeing resources from the native socket code... And just to be clear, I
>>am not failing a sanity check by keeping around strong references to
>>anything; it is definetly a mono-specific problem.
>Does http://bugzilla.ximian.com/show_bug.cgi?id=60835 look like your
>problem? I've looked at this and been unable to reproduce it, so if you
>can attach another test case for me to try I will have another go.
>Mono-devel-list mailing list
>Mono-devel-list at lists.ximian.com
More information about the Mono-devel-list