Am facing a issue similar to what we have under
[url]http://www.codecomments.com/archiv[/url]<...-11-706874.html

I work for a imaging system software and modules are a mixture of pure
ATL d
ll, "ATL using MFC" components, COM EXE servers, regular MFC dll, MFC
EXE an
d extension MFC dlls.

Now that we are towards the fag end of the project, we are getting
occasiona
lly hit by sudden crashes where our top level exception handler is not
even
able to come into play and create the required .dmp file. We also are
seeing
deadlock cases like the link I have mentioned above.

One interesting thing I found yesterday is the following

We have a MFC document view architecture based EXE component. This in
turn h
as couple of "ATL using MFC" components. These ATL components in turn
makes
call to a MFC extension dll.

I realized that we are not following all the rules as described under
[url]http://support.microsoft.com/kb/q173974/.[/url] For our "ATL using
MFC" components
Basically none of our COM interface methods and COM eventsink methods
are
using the AFX_MANAGE_STATE at all. Both COM interface methods and the
events
ink methods in turn uses MFC.

I would like to know how serious could this issue be. Could this lead
to issues as desc
ribed under
[url]http://www.codecomments.com/archive...11-706874.html.[/url]