| Bug located when calling a java class from a transformation [message #469076] |
Thu, 08 January 2009 05:42  |
Eclipse User |
|
|
|
Hello,
While creating a wrapper class for MOFScript I detected that when the
java() function is called inside a transformation for a non-static class,
the tool allocates some memory for the instance of the called class which
is never freed!! The Windows process manager shows this memory growth of
the eclipse.exe process.
Regards,
Adrian
|
|
|
|
|
|
|
|
|
| Re: Bug located when calling a java class from a transformation [message #469094 is a reply to message #469093] |
Mon, 19 January 2009 09:44  |
Eclipse User |
|
|
|
Hello Goran,
Thank you very much for your help!
However I found that the bug is still happening without making any java()
calls. It seems that the memory leak happens every time I fire a M2M
transformation.
Since the only difference between M2M and M2T transformations are the
"new" calls my guess is that the problem could be located there. I'll try
to further investigate the issue.
Thanks again and best regards,
Adrian
|
|
|
|
|
|
|
|
|
| Re: Bug located when calling a java class from a transformation [message #566330 is a reply to message #469093] |
Mon, 19 January 2009 09:44  |
Eclipse User |
|
|
|
Hello Goran,
Thank you very much for your help!
However I found that the bug is still happening without making any java()
calls. It seems that the memory leak happens every time I fire a M2M
transformation.
Since the only difference between M2M and M2T transformations are the
"new" calls my guess is that the problem could be located there. I'll try
to further investigate the issue.
Thanks again and best regards,
Adrian
|
|
|
Powered by
FUDForum. Page generated in 0.07021 seconds