We have an application that is using a shared library. The bug is exhibited
when using the shared library in a particular way.
Our application finds, loads and removes the library every time a dialog is
displayed, which causes the library to go through
its life-cycle several times within one instantiation of the application.
If we bring this dialog up >15 times, the application crashes
with a chunk overlocked crash. I was able to track this down to the
SysLibLoad call.
It is my speculation that the SysLibLoad and SysLibRemove calls are
correctly handling the handle for the shared library data
thus causing this chunk overlock. However, inspection of the library code
does not corroborate this theory as the handle and resource
gets and locks seem to be matched.
I was able to work around the problem by moving my library load into the
application start and
by moving the library remove into the application stop processing, thus
ensuring that the library is only loaded once per application
instantiation.
Kevin
__________________________
Kevin O'Keefe
The Windward Group
TEL: (408) 399-8577
FAX: (408) 395-9642
mailto:[EMAIL PROTECTED]
__________________________
