XMAX 5.5 ActiveX doesn’t let a .NET application unload from memory (on Vista?)

[akm2000]

Did anyone experience the problem?

I'm attaching zip files with Visual Studio 2008 and VS 2005 solutions.
The target .NET framework can be any 2.0 or 3.5.
The app is looking for MiniJournalist.xac, MiniJournalist.dtd and SimpleGuide.xml in the current folder.
Build the app from the source code or run the prebuilt application in bin/debug folder.

On opening you should see contents of SimpleGuide.
Now close the app. Check if the instance (BareXMetaL.exe) is still in memory (use Task Manager).
You have to kill the process manually.

Now change the name of XAC file, relocate it or change it in the source, so that XMAX couldn't find XAC and run the app again. XMAX will complain and open the document as “Well-formed” one.
Close the app. You should see no traces in memory.
So the problem may be related to XAC functionality.

Vista Enterprise SP1 32-bit, .NET 2.0 and .NET 3.5 with service packs.

Same code works fine on older machine, running XP and XMetaL 4.6.

Thanks, Andrei.

Reply

[Derek Read]

For other readers (besides akm2000 / Andrei):

The client also submitted this through our regular support channels and it is being dealt with as a standard support case. If this is a bug in XMAX, possibly triggered by VS 2008, then it is an unknown issue and we will try to address it in a future release.

Reply

[Author]

Posts