n have a problem. Submitting peta-trillion of
tasks per second can be a problem!
- Original Message -
From: "Paul Johansen" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, June 07, 2004 7:19 PM
Subject: [ADVANCED-DOTNET] ThreadPool.QueueUserWorkItem Memory Pro
f advanced .NET topics.
[mailto:[EMAIL PROTECTED] On Behalf Of Paul Johansen
Sent: Monday, June 07, 2004 2:20 PM
To: [EMAIL PROTECTED]
Subject: [ADVANCED-DOTNET] ThreadPool.QueueUserWorkItem Memory Problems
I have implemented a multithreaded solution where I am calling
ThreadPool.QueueUserWorkItem and I
Sent: Monday, June 07, 2004 1:49 PM
To: [EMAIL PROTECTED]
Subject: Re: [ADVANCED-DOTNET] ThreadPool.QueueUserWorkItem Memory
Problems
WaitCallback class ?
Are you creating a "WaitCallback" class for each queue
item?
--- Paul Johansen <[EMAIL PROTECTED]>
wrote:
> I
EMAIL PROTECTED] On Behalf Of Sam Ang
Sent: Monday, June 07, 2004 1:42 PM
To: [EMAIL PROTECTED]
Subject: Re: [ADVANCED-DOTNET] ThreadPool.QueueUserWorkItem Memory
Problems
How about setting your state object to null at the end
of your PostData?
sam
--- Paul Johansen <[EMAIL PROTECTED]>
wrot
WaitCallback class ?
Are you creating a "WaitCallback" class for each queue
item?
--- Paul Johansen <[EMAIL PROTECTED]>
wrote:
> I have implemented a multithreaded solution where I
> am calling
> ThreadPool.QueueUserWorkItem and I am passing both
> the WaitCallback
> class (using a method called
How about setting your state object to null at the end
of your PostData?
sam
--- Paul Johansen <[EMAIL PROTECTED]>
wrote:
> I have implemented a multithreaded solution where I
> am calling
> ThreadPool.QueueUserWorkItem and I am passing both
> the WaitCallback
> class (using a method called PostDa
I have implemented a multithreaded solution where I am calling
ThreadPool.QueueUserWorkItem and I am passing both the WaitCallback
class (using a method called PostData) as well as the state object (a
custom class consisting of four strings and a bool).
When I do this, I am leaking memory like
