(Memory) HeapQC finds problems on 68K

1301102

Nov 10 1995 11:54AM


HeapQC finds problems in MacApp 3.3 when testing on a 68K system. It's easy to reproduce: HeapQC starts finding problems as soon as the app is launched. It's probably our segment loading code.
HeapQC (with every switch except "Test System Heap" turned on) revealed the following problems running a Classic 7.5 build:

(1) When saving a document, HeapQC causes an exception in TFileBasedDocument::DoWrite, as it calls this->DoWritePrintInfo(), complaining that ReleaseResource was called on a non-resource. You may step through this, and continue.

(2) When opening a document, HeapQC causes a crash in TApplication::ChooseDocument when it is calling CustomGetFile. The crash actually occurs in the PACK and LDEF code.


Fix:

No longer a problem.