home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 2
Submit: Code Patches
Seek by clicking on video progress bar
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="morpheus_xx" data-source="post: 1117068" data-attributes="member: 48495"><p>One thing we need to consider here: the life time of resources is quite complicated in MPF. We have a "DeepCopy" logic to make sure that resources can be freed when they are no longer needed.</p><p></p><p>There are following types of "resource lifetimes" (I hope this list is complete, as Albert wrote the logic):</p><ul> <li data-xf-list-type="ul">Style resources: remain in memory as long as application runs</li> <li data-xf-list-type="ul">Screens: remain active once Workflow is in its state. After workflow transitions into a new workflow state, resources of former screen can be GCed</li> </ul><p>When you deal with static event handler registration this could potentially introduce references that avoid proper GC. This needs to be checked thoroughly</p></blockquote><p></p>
[QUOTE="morpheus_xx, post: 1117068, member: 48495"] One thing we need to consider here: the life time of resources is quite complicated in MPF. We have a "DeepCopy" logic to make sure that resources can be freed when they are no longer needed. There are following types of "resource lifetimes" (I hope this list is complete, as Albert wrote the logic): [LIST] [*]Style resources: remain in memory as long as application runs [*]Screens: remain active once Workflow is in its state. After workflow transitions into a new workflow state, resources of former screen can be GCed [/LIST] When you deal with static event handler registration this could potentially introduce references that avoid proper GC. This needs to be checked thoroughly [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 2
Submit: Code Patches
Seek by clicking on video progress bar
Contact us
RSS
Top
Bottom