Bug 82324 - [osgi] Unload manifest from memory
Summary: [osgi] Unload manifest from memory
Status: RESOLVED WONTFIX
Alias: None
Product: Equinox
Classification: Eclipse Project
Component: Framework (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: equinox.framework-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: performance
Depends on:
Blocks:
 
Reported: 2005-01-06 10:26 EST by Pascal Rapicault CLA
Modified: 2006-04-06 16:59 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Pascal Rapicault CLA 2005-01-06 10:26:35 EST 
Once a manifest has been loaded in memory it is never unloaded. This leads to a
big memory consumption which can be bad in big configurations. Moreover I
believe that the manifest are usually sporadicly used.
Comment 1 Michael Fraenkel CLA 2005-03-26 15:16:14 EST 
The manifest that is stored in EclipseClasspathEntry is used for each package
that needs to be defined.  Not really sure how you would know when its safe to
remove.  You could reduce the number of Manifests that are active with a cache
assuming that multiple packages from the same EclipseClasspathEntry are defined
relatively close together.
Comment 2 Mike Wilson CLA 2005-04-25 13:32:39 EDT 
How much memory are we actually talking about here? Has the internal representation been optimized 
to reduce its size?
Comment 3 Thomas Watson CLA 2005-04-27 17:19:44 EDT 
This is related to bug 91446.  It would be better to not even load the 
manifests into memory if we cached whether the manifest has package info and 
not loading it if no package info is available.
Comment 4 Pascal Rapicault CLA 2006-04-06 16:59:19 EDT 
Closing as wontfix since no one specify package info in eclipse.