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
Development
General Development (no feature request here!)
Question on garbage collection
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="draktheas" data-source="post: 29257" data-attributes="member: 17330"><p>Generally speeking, it sounds like a resource contention issue. The transcoding is running in a seperate thread locking and unlocking resources and probably allocating/deallocating (indirectly) a lot of memory. </p><p></p><p>One call to GC.Collect() should suffice for freeing all unreferenced memory. I don't know why three calls would be neccessary. The GC.GetTotalMemory call will need to temporarily lock any managed memory resources in order to obtain a snapshot of their size. My guess is that the transcoding thread is accessing a sufficient number of memory resources that it is gaining far more access to them than the GetTotalMemory call can, thus slowing down the call to GetTotalMemory.</p><p></p><p>Just my 2 cents,</p><p>Drak</p></blockquote><p></p>
[QUOTE="draktheas, post: 29257, member: 17330"] Generally speeking, it sounds like a resource contention issue. The transcoding is running in a seperate thread locking and unlocking resources and probably allocating/deallocating (indirectly) a lot of memory. One call to GC.Collect() should suffice for freeing all unreferenced memory. I don't know why three calls would be neccessary. The GC.GetTotalMemory call will need to temporarily lock any managed memory resources in order to obtain a snapshot of their size. My guess is that the transcoding thread is accessing a sufficient number of memory resources that it is gaining far more access to them than the GetTotalMemory call can, thus slowing down the call to GetTotalMemory. Just my 2 cents, Drak [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Development
General Development (no feature request here!)
Question on garbage collection
Contact us
RSS
Top
Bottom