[
https://issues.apache.org/jira/browse/GROOVY-7484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14642973#comment-14642973
]
Dmitry Baev commented on GROOVY-7484:
-------------------------------------
{quote}
The problem is actually easy to solve with a workaround... share the runtime
for the loaders. Meaning make one classloader for the runtime, and one for the
scripts as a child to that loader. This way the classes of the runtime are
shared.
{quote}
I tried to use the same workaround before submitting the issue. And it works
only if you use system class loader with groovy runtime as the parent. But If I
create the other UrlClassLoader without parent with groovy runtime it still
leak.
So in my case I can not use the system class loader as the parent
> Permgen leak when load groovy classes via reflection
> ----------------------------------------------------
>
> Key: GROOVY-7484
> URL: https://issues.apache.org/jira/browse/GROOVY-7484
> Project: Groovy
> Issue Type: Bug
> Affects Versions: 2.4.3
> Reporter: Dmitry Baev
>
> PermGen leak when load groovy beans via reflection using different class
> loaders. Sample project to reproduce the problem
> https://github.com/baev/groovy-permgen-leak
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
