GC Bug .net 2.0.50215
- From: Arthur M. <ArthurM@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 11 May 2005 08:20:08 -0700
Async functionality prevents an object from garbage collection.
To reproduce:
Create a socket
establish connection
Create NetworkStream with Ownership Of a socket (or just work socket directly)
Call BeginReceive on stream or socket
dereference network stream
The conneciton will stay up until parent process is terminated.
What GC should be doing is releasing a handle of an underlying socket which
it does not.
pseudo code:
void init()
{
init socket
socket.connect()
init networkstream(owns the socket)
networkstream.beginread(async parameters)
}
void main()
{
for (int j = 0; j < 100; j++)
{
init();
}
GC.Collecti();
GC.WaitForPendingFinalizers();
break here (console read)
}
netstat will show 100 established connections that will never go away.
.
- Follow-Ups:
- RE: GC Bug .net 2.0.50215
- From: Cowboy (Gregory A. Beamer) - MVP
- RE: GC Bug .net 2.0.50215
- Prev by Date: CultureInfo UseUserOverride short time format not available W2K
- Next by Date: Using assemlby without depending on it
- Previous by thread: CultureInfo UseUserOverride short time format not available W2K
- Next by thread: RE: GC Bug .net 2.0.50215
- Index(es):
Relevant Pages
|
