I have a multithreaded application that runs using a custom thread pool class. The threads all execute the same function, with different parameters.
These parameters
If you try to delete an object twice, the second time will fail, because the heap is already freed. This is the normal behavior.
Now, since you are in a multithreading context... it might be that the deletions are done "almost" in parallel, which might avoid the error on the second deletion, because the first one is not yet finalized.