C#•2y ago

Creating a thread that lives for as long as the application.

I wrote a server using a c library, I created two threads using

new Thread

new Thread

new Thread

new Thread

and have an infinite loop running in the threads method. One thread handles all socket related code, and adds incoming packets to be deserialized to a single producer single consumer queue. The other thread deserializes the packets. The codes works but it has a flaw. Creating the thread via

new Thread

new Thread

new Thread

new Thread

fails and I get an exception if the system running the app has no more threads available. is it possible to tell the app use an existing thread if creating a new one fails:

thread = new Thread(DoWork); //this line of code throws the exception if the cpu runs out of threads
thread.IsBackground = true;
shouldRun = true;

private void DoWork()
{
    
    Init();
    while (shouldRun == true)
    {
        Consume();
        Tick();
        
    }
}

thread = new Thread(DoWork); //this line of code throws the exception if the cpu runs out of threads
thread.IsBackground = true;
shouldRun = true;

private void DoWork()
{
    
    Init();
    while (shouldRun == true)
    {
        Consume();
        Tick();
        
    }
}

thread = new Thread(DoWork); //this line of code throws the exception if the cpu runs out of threads
thread.IsBackground = true;
shouldRun = true;

private void DoWork()
{
    
    Init();
    while (shouldRun == true)
    {
        Consume();
        Tick();
        
    }
}

thread = new Thread(DoWork); //this line of code throws the exception if the cpu runs out of threads
thread.IsBackground = true;
shouldRun = true;

private void DoWork()
{
    
    Init();
    while (shouldRun == true)
    {
        Consume();
        Tick();
        
    }
}

jcotton42•8/1/24, 5:51 AM

uh, if the OS has run out of threads, there's nothing you can do

jcotton42•8/1/24, 5:52 AM

that being said, you probably want to use tasks, not an explicit thread

Jjcotton42 that being said, you probably want to use tasks, not an explicit thread

ChezZOP•8/1/24, 5:55 AM

aren't tasks just meant for one time operations? The threads live for the life of the application.

jcotton42•8/1/24, 5:56 AM

eh, yes and no

jcotton42•8/1/24, 5:56 AM

but, socket stuff is async anyhow

jcotton42•8/1/24, 5:56 AM

so you'll be awaiting a lot

Jjcotton42 so you'll be awaiting a lot

ChezZOP•8/1/24, 6:05 AM

im not using c# sockets its using a c library no awaiting

jcotton42•8/1/24, 6:05 AM

canton7•8/1/24, 7:21 AM

What exactly is the text of the exception?

canton7•8/1/24, 7:22 AM

There's no hard limit on the number of threads (at least in Windows). It doesn't "run out" of threads. It can run out of memory to use as stack space for threads, but that'll happen at many hundreds of thousands

Ccanton7 What exactly is the text of the exception?

ChezZOP•8/1/24, 6:02 PM

each app calls new thread twice, after exactly 4 instances of my app is running the 5th will get null reference exceptions when calling thread.Start cause var thread = new Thread returns null

jcotton42•8/1/24, 6:04 PM

The OS can support thousands of threads.
Something is wrong.

ChezZOP•8/1/24, 6:10 PM

hmm

ChezZOP•8/1/24, 6:10 PM

let me try something

ChezZOP•8/1/24, 6:17 PM

ok prior to calling thread.start my custom pool allocator was failing to allocate the memory needed

ChezZOP•8/1/24, 6:27 PM

yeah my system runs out of memory after so many instances

ChezZOP•8/1/24, 6:27 PM

oops

Creating a thread that lives for as long as the application.

Similar Threads

Similar Threads

Similar Threads