When the program starts, it checks for the amount of threads the user wants to use to download files with. The threads are then created. When the user chooses a file to download, the threads begin grabbing the file until it's fully downloaded.
The problem is, some threads stall right from the start, & just sit there doing nothing.
The global work variable is Sync-Locked, then quickly released by each instance, & to my eyes, there is nothing wrong.
They are all instances of the same class, & do the exact same thing, so why is it that some run, & others don't?
VB.NET is the programming language. They are looping Background workers.
I would really like to know why some run, & others don't.
btw... they have quick non-blocking sleeps, as well as blocking sleeps to allow others the chance to run (proprietary non-blocking DLL).
So all i'm left to think on is that Microsoft's process queuing has some type of bug going on in there someplace.
Can anyone verify this?
...or is there a way to do multiple looping threads where they're guaranteed to run?
Any help will be awesomely appreciated.
The problem is, some threads stall right from the start, & just sit there doing nothing.
The global work variable is Sync-Locked, then quickly released by each instance, & to my eyes, there is nothing wrong.
They are all instances of the same class, & do the exact same thing, so why is it that some run, & others don't?
VB.NET is the programming language. They are looping Background workers.
I would really like to know why some run, & others don't.
btw... they have quick non-blocking sleeps, as well as blocking sleeps to allow others the chance to run (proprietary non-blocking DLL).
So all i'm left to think on is that Microsoft's process queuing has some type of bug going on in there someplace.
Can anyone verify this?
...or is there a way to do multiple looping threads where they're guaranteed to run?
Any help will be awesomely appreciated.
Comment