In the following code from the MTS_SampleApp if I use the variant with "LoadAse Example" and if I load an ase and then close the application on the line services = 0 appears a memory leak.How can this be solved? I have traced the problem until I have reached the code from CXPCOMObj and the asm code for CXPSafeIncr but there I got stucked. The problem seems to be related to the unloading of the "ijl10.dll" (Intel JPEG Library).

SDK_Initializer::~SDK_Initializer()
{
// the scene should be deleted first
if (scene)
{
scene->Terminate();
scene = 0;

// the scene should be deleted before the repository
// we may then check if everything was removed from the repository
}

// now we can check with the repository if everything was released
if (repository)
{
repository->Terminate();
repository = 0;
}

// the context should be deleted before the services
// because the destruction of the services will check if all dlls have been unload
context = 0;

// services should be deleted last
services = 0;
mouseunknown = 0;
}

It may be a bug. What tool are you using to detect memory leaks ?

Did we ever get a solution to this problem?

I do get the same error, but my scenario takes a different path. I load the ase, and imidiatly after publish it. For most ase file, it works, but some fails(like 1%). The ase files are working, since when doing the same in scenebuilder, everything works.

Have you persued this question Niko, or is it "done". I have an ase file you can test with to check the problem if you like.

i can't remember if we came to a solution. i wonder if some posts in the forum have been deleted or not. i know there has been some problems like that in the past when we changed the server.
Anyway gooky, i have your ASE file and we're looking into it.

Just so anyone can benifit from the answer:

The assertion is triggered by some bad polygons the content, which can be ignored.
In Release mode the assertions are def'ed out, so MTS_ScampleApp Release handles this file smoothly.

That is, just build the app in release mode