I've been using ATL for a few months, both regular ATL and EMFTVM, and I have been noticing that no matter what the heap space of my Eclipse is, eventually it gets full after running a few ATL transformations.
This means that Eclipse keeps going slower and slower and at some point I'm forced to restart it so that it can work smooth again, if I don't restart it by myself I will just get eventually an error due to the heap space forcing me to close Eclipse.
Is this an ATL issue? is there a way to solve it or prevent it? has someone else noticed it?
For me his happens only if i'm writing/testing transforms which fail for some reason i.e. throw Exceptions. In our production system which has "no known fatal errors" the heap space stays consistent.
I use both UML and Ecore and I don't see this happen. The stack always goes back to the level it was at before, even for massive long running transforms. Perhaps you are using the ATL Menu Launcher (Run Configuration)? I only use this when testing and perhaps that is why I see such issues there when the transforms fail. For production I always use the ATL Launcher API from org.eclipse.m2m.atl.core
You could try using the API or the ANT tasks and see if that helps.
you're completely right, I'm using the ATL menu launcher, is it somehow bugged when working with UML2? I have used ANT tasks in the past, I never used the API, though I guess if I have to I will but I'd rather keep things as they are.
I will run some tests with ANT tasks and see if it is still troublesome, I'll let you know what I find out.