[
https://issues.apache.org/jira/browse/ARIES-1909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17779269#comment-17779269
]
Heiko Studt commented on ARIES-1909:
------------------------------------
This issue was from 2019 about a 32 bit computer, is this still active?
I assume you are referring to the BlueprintContainerImpl within blueprint-core.
There is some local state machine. The parser is initialized within the initial
state (Unknown) and used within several states. To my reading, you want to
remove the parser instance, after the state has reached Created or Failed!?
However, these are not "final states" as the state machine can be reset to
Unknown by reload() doing a re-instantiating of the parser for this container,
or WaitForNamespaceHandlers by namespaceHandlerUnregistered which does not
re-instantiate the parser instance and would therefore break.
> parser class member is never released in BlueprintContainerImpl
> ---------------------------------------------------------------
>
> Key: ARIES-1909
> URL: https://issues.apache.org/jira/browse/ARIES-1909
> Project: Aries
> Issue Type: Bug
> Components: Blueprint
> Affects Versions: blueprint-core-1.10.2
> Environment: Windows 32 bits / JVM 8 32 bit
> Reporter: stephane
> Priority: Critical
>
> We use OSGI framework within a project under a JVM8 / 32 Bits / Windows 7.
> Our heap is set to 650Mo (cannot be more due to native memory + metaspace and
> the fact that a process under Windows 32 bits / JVM 32 bit cannot be more
> than 1.5Go).
> At runtime we have around 200Mo of left heap memory. Inside these 200Mo we
> have 35Mo of data retained by the parser used at init time of the containers.
> It seems that this parser is only used at init time.
>
> Would it be possible to set it to null? it will free-up 15% of our heap and
> it is huge for us.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
