You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Richard S. Hall (JIRA)" <ji...@apache.org> on 2008/12/18 22:03:44 UTC
[jira] Closed: (FELIX-835) Module is not removed from factory after
failed install/update
[ https://issues.apache.org/jira/browse/FELIX-835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Richard S. Hall closed FELIX-835.
---------------------------------
Resolution: Fixed
Committed a fix to properly dispose of the created module.
> Module 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.