Task.run creates out of memory exception in C#

Question

0.00/5 (No votes)

See more:

I am working with the following logic:

if (testList.Count >= 512)
{
double[] testarry = testList.ToArray();
Task.Run(() => SendMessage(testarry));
testList.Clear();
}
I have to SendMessage every 300 milli-second and it takes close to 400 milliseconds to send message after processing. So I thought of using Task.Run which I believe creates a new task on every call. But my program gives out of memory exception after running for few hours. Can anyone help me out?

What I have tried:

I thought of using a single task but since my processing takes more time, I may miss out some points

Posted 2-May-18 6:39am

Member 13245297

Updated 2-May-18 6:51am

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Answer 1 · 2018-05-02T06:53:00

If it takes 400ms to send, and you send it every 300ms, then it doesn't matter how many threads you start: you will still have exactly the same problem, just very slightly delayed, or even slightly sooner. Think about it: once your processor runs out of free cores, the threads you kick off will be suspended waiting for their turn to run (since a thread, or "task" needs a free core in order to run).

Boosting the number of threads will probably make the problem worse, not better, because each thread adds both a memory and a processing overhead to the system.

The only way to prevent the problem is to speed up the message sending, or slow down the send rate.