You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@poi.apache.org by "Dominik Stadler (JIRA)" <ji...@apache.org> on 2019/03/03 09:06:00 UTC
[jira] [Resolved] (XMLBEANS-537) MemoryLeak in SchemaCompiler
[ https://issues.apache.org/jira/browse/XMLBEANS-537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dominik Stadler resolved XMLBEANS-537.
--------------------------------------
Resolution: Fixed
Assignee: Dominik Stadler
Fix Version/s: Version 3.0.3
Should be fixed via https://svn.apache.org/r1854678 now.
> MemoryLeak in SchemaCompiler
> ----------------------------
>
> Key: XMLBEANS-537
> URL: https://issues.apache.org/jira/browse/XMLBEANS-537
> Project: XMLBeans
> Issue Type: Bug
> Components: Compiler
> Affects Versions: Version 3.0.2
> Reporter: Thorsten Goetzke
> Assignee: Dominik Stadler
> Priority: Major
> Fix For: Version 3.0.3
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Both org.apache.xmlbeans.impl.tool.SchemaCompiler and org.apache.xmlbeans.impl.schema.SchemaTypeSystemCompiler use
> {{StscState start}}
> But only SchemaTypeSystemCompiler uses
> {{StscState end}}
> This breaks Class unloading. Highly relevant because the ant task org.apache.xmlbeans.impl.tool.XMLBean uses SchemaCompiler which means ant builds are leaking class definitions.
> Please add
> {{StscState end}}
> to SchemaCompiler as well
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
For additional commands, e-mail: dev-help@poi.apache.org