[
https://issues.apache.org/jira/browse/CALCITE-3759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17026911#comment-17026911
]
Rui Wang commented on CALCITE-3759:
-----------------------------------
Ah I misunderstood what class leak meant in this Jira: I thought that meant
Calcite releases some classes that does not belong to Calcite (e.g. class name
not start from org.apache.calcite). But seems like the class leak talked about
here is objects stay in memory and not GCed forever. Sorry I wasn't helpful at
the beginning.
> Class memory leak due to code generation
> ----------------------------------------
>
> Key: CALCITE-3759
> URL: https://issues.apache.org/jira/browse/CALCITE-3759
> Project: Calcite
> Issue Type: Bug
> Components: core
> Affects Versions: 1.21.0
> Reporter: Mike Villa
> Priority: Major
> Attachments: image-2020-01-28-15-55-43-215.png
>
>
> Hi, I'm using calcite and I'm making unit test to see the perform, but with
> visualvm or jconsole I have checked a class leak. Maybe It's my fault.
> I would be grateful if someone helped me to find the error!
> I have created a GitHub project to check this error.
> https://github.com/mvillafuertem/calcite-error.git
>
> !image-2020-01-28-15-55-43-215.png!
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
