Assert error once I exit indesign

Question

Hi All.,
I am developing a plugin for my client. The plugin seems to working fine. But once I close the plugin window and exit indesign I get an assertion error followed by memory leaks message.
I am posting the error below:
~InstanceList(): 1 outstanding references to UID 9001 (Class Unknown3rdPartyPrefix + 6 (0xfe606)).
\Development\firedrake\source\components\database3\main\InstanceList.cpp (1784)
~InstanceList(): 2 outstanding references to UID 4160 (Class ShuksanPrefix + 8 (0x108)).
~InstanceList(): 1 outstanding references to UID 4159 (Class ShuksanPrefix + 8 (0x108)).
~InstanceList(): 1 outstanding references to UID 25 (Class ShuksanPrefix + 8 (0x108)).
Can somebody provide me a solution.
Thanks
Vishnu

Answer 1

Hi!<br /><br />Dunno if this helps you (from ww-plugin.pdf, page 36):<br /><br />Generally, Query*** methods (commonly known as bridge methods, see Using databases and<br />objects in plug-ins on page 37) return a pointer to an interface derived from IPMUnknown,<br />and also increment the reference count. However, you would still like to take advantage of the<br />automated cleanup provided by InterfacePtr. To prevent reference counts from incrementing,<br />like in Type 1a and 1b, use this constructor, which does not call IPMUnknown::AddRef:<br />InterfacePtr<IGeometry> iPageGeometry(iSpread->QueryNthPage(0));<br />The following line of code looks perfectly innocent, but if you execute this and quit InDesign,<br />then you will get a boss leak:<br />InterfacePtr<IGeometry> iPageGeometry(iSpread->QueryNthPage(0), UseDefaultIID());<br />Look carefully: ISpread->QueryNthPage(0) increments the reference count and also, by means<br />of InterfacePtr constructor Type 1a, the reference count increments again.<br />The easiest remedy is to remove UseDefaultIID. However, if you leave it as is, and fail to notice<br />that a call to iPageGeometry->Release is necessary, you will get a boss leak.<br /><br />Short version: If you create an InterfacePtr with QuerySomething, I think you have to release it afterwards.