[
https://issues.apache.org/jira/browse/FELIX-835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Pauls updated FELIX-835:
-----------------------------
Component/s: Framework
Fix Version/s: felix-1.4.1
Assignee: Richard S. Hall
Description: When a bundle is installed or updated we create a module
in Felix.createModule and add it to the factory. If an exception is thrown
later (e.g., because there is a native library missing) the module is not
removed. We do clean up the contentloader, the archive, and the bundle so it is
not a big memory leak but it might be a small one. Furthermore, it is possible
that this might screw up subsequent resolves. We need to revisit that when
we're done with the current resolver refactoring.
Affects Version/s: felix-1.4.0
Summary: Modules is not removed from factory after failed
install/update (was: Modules of failed install/update is not removed)
> Modules is not removed from factory after failed install/update
> ---------------------------------------------------------------
>
> Key: FELIX-835
> URL: https://issues.apache.org/jira/browse/FELIX-835
> Project: Felix
> Issue Type: Bug
> Components: Framework
> Affects Versions: felix-1.4.0
> Reporter: Karl Pauls
> Assignee: Richard S. Hall
> Priority: Minor
> Fix For: felix-1.4.1
>
>
> When a bundle is installed or updated we create a module in
> Felix.createModule and add it to the factory. If an exception is thrown later
> (e.g., because there is a native library missing) the module is not removed.
> We do clean up the contentloader, the archive, and the bundle so it is not a
> big memory leak but it might be a small one. Furthermore, it is possible that
> this might screw up subsequent resolves. We need to revisit that when we're
> done with the current resolver refactoring.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
