CgDisplay, CgPrinterWindow, CgPrinterScreen instance growth

[waynej]

We have a simple 7.5.1 application that periodically creates a VAST report and prints it. We've noticed a memory leak. The number of instances of CgDisplay, CgPrinterWindow, CgPrinterScreen, OSDevmode and other classes keeps growing. I haven't found the right thing to cause these things to get cleaned up. We create a AbtReportPrinter and it does get garbage collected. We get a AbtAppBldrReport subclass instance and we call #destroyPart on it, and these instances do get garbage collected. Is there some thing I am missing in order to free these other things up? Or should we instead try to hold onto the AbtReportPrinter instance to avoid creating new objects? That's what a 'sister' project did to solve the problem in their application.

[Diane Engles]

You might consider using the methods allReferences and allInstances in the context of GF/ST's Visual Inspectors.

GF/ST ships as as an unsupported goodie in version 7.x and 8.0. The documentation is in the installation readme directory and is titled Gfst70.pdf. Look in Appendix A for the Visual Inspector documentation.

There are two inspectors: the PsiVisualInspector and SmsVisualInspector that offer some extra features that may allow you to better explore references to your objects which are not getting cleaned up .

You could send a message such as MyClassOfInterest allReferences psiVisualInspect and a graphical inspector will open which lets you visually explore the objects which are referencing the class of interest. Also look at the class comment of SmsVisualInspecting for another way to inspect.

You will need to load the configuration map VisualInspector [TM] IBM/ST.