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 1
MediaPortal 1 Talk
Memory leak in TVService
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="Brownard" data-source="post: 1283461" data-attributes="member: 48291"><p>That sounds about right, the GC runs when it detects memory 'pressure', which is pretty complicated but an oversimplified version would be it runs when memory usage is already quite high relative to the rest of the OS and it needs to allocate more memory. This is different to what is often intuitively expected, the GC doesn't necessarily free up memory after it's finished with it or try and keep memory usage as low as possible (because the GC requires that the entire app is 'paused' whilst it marks what memory can be freed which is obviously detrimental to app responsiveness), but will hang on to it until the next time a big allocation is needed which takes it over some calculated limit. For something like the TV server that might sit idle for hours/days this can mean that the GC doesn't run for hours/days until something like the EPG runs and allocates a load of stuff, which then triggers a GC which frees all of the unused memory and causes a potentially big drop.</p></blockquote><p></p>
[QUOTE="Brownard, post: 1283461, member: 48291"] That sounds about right, the GC runs when it detects memory 'pressure', which is pretty complicated but an oversimplified version would be it runs when memory usage is already quite high relative to the rest of the OS and it needs to allocate more memory. This is different to what is often intuitively expected, the GC doesn't necessarily free up memory after it's finished with it or try and keep memory usage as low as possible (because the GC requires that the entire app is 'paused' whilst it marks what memory can be freed which is obviously detrimental to app responsiveness), but will hang on to it until the next time a big allocation is needed which takes it over some calculated limit. For something like the TV server that might sit idle for hours/days this can mean that the GC doesn't run for hours/days until something like the EPG runs and allocates a load of stuff, which then triggers a GC which frees all of the unused memory and causes a potentially big drop. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
MediaPortal 1 Talk
Memory leak in TVService
Contact us
RSS
Top
Bottom