[omniORB] omni_thread::init_t::~init_t will leak when FreeLibrary is called from a different thread as LoadLibrary

[Duncan Grisby]

On Monday 9 June, Martin Trappel wrote:

> Do you expect any problems from loading the omniThread DLL from a
> thread that later goes away? (That would mean self() on the main
> thread will fail?) I can live with the two(2) memory leaks due to the
> fact that the unloading is not completed, but may there be other
> problems?

The thread that loads the omnithread dll is considered to be the main
thread. As long as you aren't using the main thread POA policy, it
doesn't matter if that thread goes away. I don't think there will be any
ill effects other than the small leak.

Cheers,

Duncan.

-- 
 -- Duncan Grisby         --
  -- duncan at grisby.org     --
   -- http://www.grisby.org --