But that raises the question, what is worse, killing it completely or leaving an object in an unknown state?
If you kill one, then the object it was holding is STILL in an unknown state, so why not just force it to release the object so the other one can run, instead of killing it completely?
That also raises the question of whether either will produce viable results. being that the object could have been altered in some manner to effect the outcome of the other.
Either way the results can't be trusted.
kill em both and start over!
You make an excellent point...
An example scenario is a production line in which there is a object to create labels and another one to select the the product size... If process A is printing out labels size 8, while waiting for the product size object... And process B is not doing anything
because its waiting for the label maker... If the OS decides to release A's object, then B will run but try and put the wrong size product into the already produced labels.
Just a correction, we're Czech not Czeck
Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation, please create a new thread in our Forums, or Contact Us and let us know.