You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Karl Pauls (Jira)" <ji...@apache.org> on 2020/07/07 20:49:00 UTC
[jira] [Resolved] (FELIX-6297) unclosed InputStream on Bundle.start
[ https://issues.apache.org/jira/browse/FELIX-6297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Karl Pauls resolved FELIX-6297.
-------------------------------
Resolution: Fixed
I merged your PR - Thanks!
> unclosed InputStream on Bundle.start
> ------------------------------------
>
> Key: FELIX-6297
> URL: https://issues.apache.org/jira/browse/FELIX-6297
> Project: Felix
> Issue Type: Bug
> Components: Framework
> Affects Versions: framework-6.0.3
> Environment: windows 10, java11
> Reporter: Jason P. Leasure
> Assignee: Karl Pauls
> Priority: Major
> Labels: framework, leak
> Fix For: framework-6.0.4
>
>
> This bug was first observed on Windows 10: An exploded bundle with an activator is started then uninstalled. A handle to the bundle's manifest is held by the JVM until shutdown so, in particular, the Manifest can't be modified or deleted.
> This is caused by an unclosed {{InputStream}}:
> When Java major version is greater than 8 and a Bundle with an activator is started,
> {{org.apache.felix.framework.util.MultiReleaseContent.wrap}} is called. It calls {{Content.getEntryAsAstream}} and the resulting {{InputStream}} is neither closed nor returned.
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)