Clearing Java Objects

Question

Joseph Burgel 2011-6-21

0
链接

此问题的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/9981-clearing-java-objects

My code uses Java objects that I created and provide to ML in a .jar file.

After my code terminates, I try to run "clear java" and I get a message back that some of my objects still exist and Java cannot be cleared:

Warning: Objects of Param/TableCellRenderer class exist - not clearing java Warning: Objects of Param/RowHeaderRenderer class exist - not clearing java

How can I clear these objects? The only way that I have found is to restart ML. Not fun when co-developing between ML and Java.

3 个评论
显示 1更早的评论隐藏 1更早的评论

Joseph Burgel 2011-6-27

Hi Kaustubha,

No, that's not the case. As and experiment, I removed my .jar file from the Java dynamic class path and added it to the static class path by modifying classpath.txt and re-starting Matlab. Guess what...the problem went away. So, this problem lies in the fact that ML is not properly de-referencing java objects on the dynamic classpath. Or, some aspect of my .java code is causing it not to be properly de-referenced when it's on the dynamic classpath. I have other java objects that don't have this problem and work fine on the dynamic path. Can anyone shed some light on why this might be. Thanks.

Kaustubha Govind 2011-6-27

Interesting problem. You might want to consider contacting Tech Support to see if they've seen this before.

请先登录，再进行评论。

请先登录，再回答此问题。

Answer 1

Joseph Burgel 2011-6-28

2
链接

此回答的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/9981-clearing-java-objects#answer_14363

As an experiment, I removed my .jar file from the Java dynamic class path and added it to the static class path by modifying classpath.txt and re-starting Matlab. Guess what...the problem went away. So, this problem lies in the fact that ML is not properly de-referencing java objects on the dynamic classpath. Or, some aspect of my .java code is causing it not to be properly de-referenced when it's on the dynamic classpath. I have other java objects that don't have this problem and work fine on the dynamic path.