I am creating IEImage objects in background threads, there can be concurrent calls to IEImage constructor.
What I noticed is that sometimes I get AccessViolationException, and sometimes the calls just hang.
I am using IEImage just localy (creating image, loading it, converting to .NET image (GetNetImage) or saving it to memory stream and then immediately disposing it. Each instance is used in one thread only.
Should this work? Or there is a general issue when using IEvolution in multithreading environment?