yang686526

crash in odgsuninitialize depending on active model/paper sp
crash in odgsuninitialize depending on active model/paper space of dwg in vectorize d
hello,
i'm trying to develop with vs 2005 the vectorizing dll for dwg files using opendesign 2.4.1.
my project is simply mfc statically linked dll with few functions for opening dwg file, device initialization with hwnd,
and finally drawing the dwg in client application window.
this dll is build as the odvectorizeex sample with its own device class (codedeviceublic exgsgdivectorizedevice) and
its own view class (codeview : public exgdivectorizeview).
in the initdevice fuction :
odgsdeviceptr pdevice = exgsscreendevice<codedevice>::createobject();
(static_cast<codedevice*>(pdevice.get()))->sethwnd( oduint32( hwnd ) );
m_pdevice = oddbgsmanager::setupactivelayoutviews(pdevice, m_pdbcontext);
the test application and the vectorixe dll works fine with dwg files saved with the model space active.
the problem is with dwg files saved with paper layout active.
after proper vectorization of such file in the window of test application i got
<<unhandled exception - access violation reading location during closing application.>>
the exception is generated in the odgsuninitialize called in the exitinstance of dll.
below is the call stack of the problem:
oda.dll!odarray<int,odmemoryallocator<int> >::length() line 919 + 0xf bytes c++
oda.dll!odarray<int,odmemoryallocator<int> >::append(const int & value=2) line 1003 + 0x13 bytes c++
oda.dll!odslotmanager::freeslot(unsigned int slotid=2) line 82 c++
oda.dll!odgsbasevectorizeview::~odgsbasevectorizev iew() line 427 c++
oda.dll!exgdivectorizeview::~exgdivectorizeview() + 0xd2 bytes c++
oda.dll!codeview::~codeview() line 10 + 0x8 bytes c++
oda.dll!odrxobjectimpl<codeview,odgsview>::~odrxob jectimpl<codeview,odgsview>() + 0x2b bytes c++
oda.dll!odrxobjectimpl<codeview,odgsview>::`scalar deleting destructor'() + 0x2b bytes c++
oda.dll!odrxobjectimpl<codeview,odgsview>::release () line 77 + 0x34 bytes c++
oda.dll!odsmartptr<odgsview>::release() line 274 + 0x15 bytes c++
oda.dll!odsmartptr<odgsview>::~odsmartptr<odgsview >() line 260 c++
oda.dll!odgspaperlayouthelperimpl::~odgspaperlayou thelperimpl() + 0x38 bytes c++
oda.dll!odrxobjectimpl<odgspaperlayouthelperimpl,o dgspaperlayouthelperimpl>::~odrxobjectimpl<odgspap erlayouthelperimpl,odgspaperlayouthelperimpl>() + 0xf bytes c++
oda.dll!odrxobjectimpl<odgspaperlayouthelperimpl,o dgspaperlayouthelperimpl>::`scalar deleting destructor'() + 0xf bytes c++
oda.dll!odrxobjectimpl<odgspaperlayouthelperimpl,o dgspaperlayouthelperimpl>::release() line 77 + 0x20 bytes c++
oda.dll!odsmartptr<odgsdevice>::release() line 274 + 0x15 bytes c++
> oda.dll!codaapp::exitinstance() line 134 c++
additionally i have created simply mfc application (not dll) with the same classes and function call sequence and it works fine in both cases: with model and paper space active.
thanks in advance for any help.
phd eng. piotr narowski
institute of heating and ventilation
warsaw unversity of technology
you should free m_pdevice, before oduninitialize(), like all the other dd objects. active space should be irrelevant.
vladimir
quote:
originally posted by wvk
you should free m_pdevice, before oduninitialize(), like all the other dd objects. active space should be irrelevant.
thank you i did it but nobody nowhere wrote that first you shoud release m_pdevice and next the m_pdb connected with this device. the release order is very important!!! in the samples it is done prperly because mfc first destroys the view and next the document.
thanks for reply.
phd eng. piotr narowski
institute of heating and ventilation
warsaw unversity of technology