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="CyberSimian" data-source="post: 1285898" data-attributes="member: 141969"><p>This suggests that the memory leak is not related to the schedule type (ETEC or ETTC). My test result of no memory leak with ETEC is consistent with this. My test was not comprehensive, and a different test might provoke the memory leak:</p><ul> <li data-xf-list-type="ul">Perhaps a single EPG grab is not sufficient, and there needs to be hundreds of EPG grabs for the memory leak to accumulate and be noticeable.</li> <li data-xf-list-type="ul">Perhaps it is the timeshift grabber that causes the memory leak.</li> <li data-xf-list-type="ul">Perhaps the memory leak occurs when a scheduled recording starts, and not when the EPG is grabbed.</li> </ul><p>My test did not test any of these possibilities. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite3" alt=":(" title="Frown :(" loading="lazy" data-shortname=":(" /></p><p></p><p>Your current setup is valuable because it seems to be able to reproduce the error consistently. The suggestion from [USER=98267]@doskabouter[/USER] of using a memory profiler to see if it is possible to identify where the memory leak is occurring is a good one. But as I have never used such a tool, I don't know how easy it would be to set it up for MP. If you have some programming experience (and the time available!), the memory profiler might be the best way to investigate this problem.</p><p></p><p>If you want simply to be able to use MP for enjoyment, and not spend hours investigating its inner workings, I would suggest that you change your EPG grabber settings, and use the ones that I suggested earlier, to make the EPG processing as simple as possible:</p><ul> <li data-xf-list-type="ul">Use the idle grabber once per day, grabbing from only one channel.</li> <li data-xf-list-type="ul">Disable the timeshift grabber (at least, for a few days).</li> </ul><p>If this avoids the memory leak, you will have a usable work-around. However, it might cause the memory leak to disappear forever from your system, and no longer be reproducible (since we don't know what exact combination of settings causes the error to occur). <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite3" alt=":(" title="Frown :(" loading="lazy" data-shortname=":(" /></p><p></p><p></p><p>I do this too. I currently have around 150 series scheduled to record, but only a small number of them are actually being broadcast at the moment. I have not encountered the memory leak with this number of series, but if you have a significantly larger number of series scheduled, that cannot be ruled out as a cause of the problem.</p><p></p><p>-- from CyberSimian in the UK</p></blockquote><p></p>
[QUOTE="CyberSimian, post: 1285898, member: 141969"] This suggests that the memory leak is not related to the schedule type (ETEC or ETTC). My test result of no memory leak with ETEC is consistent with this. My test was not comprehensive, and a different test might provoke the memory leak: [LIST] [*]Perhaps a single EPG grab is not sufficient, and there needs to be hundreds of EPG grabs for the memory leak to accumulate and be noticeable. [*]Perhaps it is the timeshift grabber that causes the memory leak. [*]Perhaps the memory leak occurs when a scheduled recording starts, and not when the EPG is grabbed. [/LIST] My test did not test any of these possibilities. :( Your current setup is valuable because it seems to be able to reproduce the error consistently. The suggestion from [USER=98267]@doskabouter[/USER] of using a memory profiler to see if it is possible to identify where the memory leak is occurring is a good one. But as I have never used such a tool, I don't know how easy it would be to set it up for MP. If you have some programming experience (and the time available!), the memory profiler might be the best way to investigate this problem. If you want simply to be able to use MP for enjoyment, and not spend hours investigating its inner workings, I would suggest that you change your EPG grabber settings, and use the ones that I suggested earlier, to make the EPG processing as simple as possible: [LIST] [*]Use the idle grabber once per day, grabbing from only one channel. [*]Disable the timeshift grabber (at least, for a few days). [/LIST] If this avoids the memory leak, you will have a usable work-around. However, it might cause the memory leak to disappear forever from your system, and no longer be reproducible (since we don't know what exact combination of settings causes the error to occur). :( I do this too. I currently have around 150 series scheduled to record, but only a small number of them are actually being broadcast at the moment. I have not encountered the memory leak with this number of series, but if you have a significantly larger number of series scheduled, that cannot be ruled out as a cause of the problem. -- from CyberSimian in the UK [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
MediaPortal 1 Talk
Memory leak in TVService
Contact us
RSS
Top
Bottom