Thread issue/leak?

I am creating a worker thread from inside an aspx page and the thread does
the stuff it should do, no problem.
However, I have noticed running it in the debugger that it seems as if the
threads are not killed/garbage-collected after a thread terminates. I have
a
breakpoint in the thread itself and every time it breaks, in the Threads
window I observe the new thread, but the previous thread is still there as
well. The exact same code in a windows app performs as expected, on every
break there are two threads, the main thread and the current worker
thread.
The simplified code below also gives the same results, so nothing strange
in
the thread itself. If I put the code in a loop of 2000 cycles and break
after the last, then there are 2000 worker threads displayed in the
Threads
window.

Dim ttt As Thread = New Thread(AddressOf TheThreadProc)
ttt.ApartmentState = Threading.ApartmentState.STA
ttt.Start()
ttt.Join()

And the simple thread:

Private Sub TheThreadProc()
Dim iii As Integer = 10
End Sub

This is because you are using a Single-Threaded Apartment. There is
nothing in the thread to receive messages. When you use COM in an ASP.Net
application, you create an Interop class that is disposable, and
therefore, the thread can be killed. IOW, don't use an STA thread unless
you are doing Interop.

--
HTH,

Kevin Spencer
Microsoft MVP
.Net Developer
Everybody picks their nose,
But some people are better at hiding it.

"Chris Botha" <ch***********@AThotmail.com> wrote in message
news:uo**************@TK2MSFTNGP14.phx.gbl...

I am creating a worker thread from inside an aspx page and the thread does
the stuff it should do, no problem.
However, I have noticed running it in the debugger that it seems as if
the
threads are not killed/garbage-collected after a thread terminates. I
have a
breakpoint in the thread itself and every time it breaks, in the Threads
window I observe the new thread, but the previous thread is still there
as
well. The exact same code in a windows app performs as expected, on every
break there are two threads, the main thread and the current worker
thread.
The simplified code below also gives the same results, so nothing strange
in
the thread itself. If I put the code in a loop of 2000 cycles and break
after the last, then there are 2000 worker threads displayed in the
Threads
window.

Dim ttt As Thread = New Thread(AddressOf TheThreadProc)
ttt.ApartmentState = Threading.ApartmentState.STA
ttt.Start()
ttt.Join()

And the simple thread:

Private Sub TheThreadProc()
Dim iii As Integer = 10
End Sub

Kevin, thanks for the response, however this is not it, I tested it
without STA before I posted the problem, same result.
The true thread is doing Interop, the simple example below is not (the
simple example produces the error/issue, with or without the STA
statement).

"Kevin Spencer" <ke***@DIESPAMMERSDIEtakempis.com> wrote in message
news:uh**************@TK2MSFTNGP15.phx.gbl...

This is because you are using a Single-Threaded Apartment. There is
nothing in the thread to receive messages. When you use COM in an ASP.Net
application, you create an Interop class that is disposable, and
therefore, the thread can be killed. IOW, don't use an STA thread unless
you are doing Interop.

--
HTH,

Kevin Spencer
Microsoft MVP
.Net Developer
Everybody picks their nose,
But some people are better at hiding it.

"Chris Botha" <ch***********@AThotmail.com> wrote in message
news:uo**************@TK2MSFTNGP14.phx.gbl...

I am creating a worker thread from inside an aspx page and the thread
does
the stuff it should do, no problem.
However, I have noticed running it in the debugger that it seems as if
the
threads are not killed/garbage-collected after a thread terminates. I
have a
breakpoint in the thread itself and every time it breaks, in the Threads
window I observe the new thread, but the previous thread is still there
as
well. The exact same code in a windows app performs as expected, on
every
break there are two threads, the main thread and the current worker
thread.
The simplified code below also gives the same results, so nothing
strange in
the thread itself. If I put the code in a loop of 2000 cycles and break
after the last, then there are 2000 worker threads displayed in the
Threads
window.

Dim ttt As Thread = New Thread(AddressOf TheThreadProc)
ttt.ApartmentState = Threading.ApartmentState.STA
ttt.Start()
ttt.Join()

And the simple thread:

Private Sub TheThreadProc()
Dim iii As Integer = 10
End Sub

Kevin, thanks for the response, however this is not it, I tested it
without STA before I posted the problem, same result.
The true thread is doing Interop, the simple example below is not (the
simple example produces the error/issue, with or without the STA
statement).

"Kevin Spencer" <ke***@DIESPAMMERSDIEtakempis.com> wrote in message
news:uh**************@TK2MSFTNGP15.phx.gbl...

This is because you are using a Single-Threaded Apartment. There is
nothing in the thread to receive messages. When you use COM in an ASP.Net
application, you create an Interop class that is disposable, and
therefore, the thread can be killed. IOW, don't use an STA thread unless
you are doing Interop.

--
HTH,

Kevin Spencer
Microsoft MVP
.Net Developer
Everybody picks their nose,
But some people are better at hiding it.

"Chris Botha" <ch***********@AThotmail.com> wrote in message
news:uo**************@TK2MSFTNGP14.phx.gbl...

I am creating a worker thread from inside an aspx page and the thread
does
the stuff it should do, no problem.
However, I have noticed running it in the debugger that it seems as if
the
threads are not killed/garbage-collected after a thread terminates. I
have a
breakpoint in the thread itself and every time it breaks, in the Threads
window I observe the new thread, but the previous thread is still there
as
well. The exact same code in a windows app performs as expected, on
every
break there are two threads, the main thread and the current worker
thread.
The simplified code below also gives the same results, so nothing
strange in
the thread itself. If I put the code in a loop of 2000 cycles and break
after the last, then there are 2000 worker threads displayed in the
Threads
window.

Dim ttt As Thread = New Thread(AddressOf TheThreadProc)
ttt.ApartmentState = Threading.ApartmentState.STA
ttt.Start()
ttt.Join()

And the simple thread:

Private Sub TheThreadProc()
Dim iii As Integer = 10
End Sub