Messages

1

Automation Interface, Add-Ins and Tools / Re: Memory usage for automation interface w/Java A

« on: October 21, 2008, 11:20:49 am »

That worked. I had read that file, but I guess I didn't understand what it said. Thanks!

2

Automation Interface, Add-Ins and Tools / Memory usage for automation interface w/Java API

« on: October 20, 2008, 11:20:21 pm »

Is there a particularly good way of tracking the memory usage of EA when using the automation interface Java API? Currently, the size of the associated EA image grows and grows during the course of my program's run until the computer grinds to a halt, but the program should not be retaining any data from the Sparx model directly (the program retrieves a number of values from a model, makes copies of those values into its own structure, and then the parts of the model referenced within the program should fall out of scope and be collected). The memory allocation does not seem to decrease significantly after the run of the Java garbage collector either (which I checked using the java -verbose:gc option and monitoring the output). Is there any way I can see what information EA is keeping around, and perhaps gain any information as to why it thinks that information should stay around?