When to destroy object created in thread, and passed to main thread in message?

[Vegar]

Hi,

In my worker, I do a soap request, resulting in a newly created object holding data return from the request. This data is passed in a message to the main thread, which updates the gui with the data.

In the workers cleanup-method, I free the created object.

This results in a exception, cause the main thread has not always processed the message before the workers cleanup method gets called.

So where should I do the cleanup? Should I let the main thread destroy the object, or can I do anything to ensure that messages is processed before cleanup is called?

regards,
-Vegar

[Primoz Gabrijelcic]

Free the object in the main thread. I do it all the time.

Passing ownership together with the data is useful semantics. You just have to keep in mind that you're doing it.

[bendeguzz]

I needed something similar, and what I did was that I wrote a 'CleanUp()' procedure, which was called via a message from the main thread, after I've done everything I needed with the object.

PS: my object had a 'Processed' boolean field, which marked if it is freeable.