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="mm1352000" data-source="post: 1283336" data-attributes="member: 82144"><p>Interesting. Okay. So in short: apparently no significant difference compared to the numbers you initially reported.</p><p></p><p>I must confess I was hoping that we'd see some change in the outcome, and that this would lead to a relatively easy resolution. This result is taking us down a harder path.</p><p></p><p>For now I only have more questions...!</p><p></p><p>1. You've said previously that your system is normally up 24/7. To make sure I've understood that statement correctly: you mean that the system is normally on, and you don't use standby, hibernate, or any other power-saving scheme - correct?</p><p></p><p>2. Without asking you to monitor more closely (...yet!): is it your current understanding/observation that memory usage just slowly creeps up over the seconds and minutes? A dripping tap that slowly but surely leaks ~20 MB per hour, as opposed to static memory usage 99% of the time followed by a burst-increase at [for example] a particular time every hour?</p><p></p><p>3. Again, without asking you to monitor more closely: is it your current understanding/observation that memory usage starts creeping up from the moment TvS starts? That, as opposed to an issue that only starts after a particular interaction - for example, after the first recording starts or live TV usage?</p><p></p><p>4. Does this system also run MP?</p><p>5. In total how many MP (client/frontend) installations use this instance of TvS?</p><p>6. Roughly speaking, what is the usage pattern for the clients? In particular, are some/any always on... or do they generally sit in standby/hibernate unless they're being actively used?</p><p></p><p>I ask the above client-related questions because at this point I honestly can't think of any other purely TvS-driven and "disableable" background tasks. That would only leave us with client interactions (which obviously can't occur when the clients are in standby or not running - hence question 6) and non-disableable tasks such as:</p><ul> <li data-xf-list-type="ul">the recording/scheduler loop ("Is it time to start or stop a recording now?"), which if I recall correctly runs every 15 seconds</li> <li data-xf-list-type="ul">the power state change monitor ("Does the system want to suspend or resume now?"), which does "stuff" every time Windows notifies us of an event we may or may not care about</li> <li data-xf-list-type="ul">the tuner detector ("Has a new tuner been connected to the system, or has an existing tuner been disconnected from the system?"), which does "stuff" every time Windows notifies us that "a device connected to the system has changed", and when UPnP devices connect to or disconnect from the network</li> <li data-xf-list-type="ul">the streaming server, which enables remote clients to stream live TV and recordings</li> </ul><p>All of these are very much core tasks, which is why they can't be disabled. A set of debug-level log files would potentially show how active the power state change monitor, tuner detector, and streaming server are. It's possible - for example - that on your particular system Windows is triggering the tuner detector more often than expected... and therefore the memory usage would be more obvious on your system than any other.</p></blockquote><p></p>
[QUOTE="mm1352000, post: 1283336, member: 82144"] Interesting. Okay. So in short: apparently no significant difference compared to the numbers you initially reported. I must confess I was hoping that we'd see some change in the outcome, and that this would lead to a relatively easy resolution. This result is taking us down a harder path. For now I only have more questions...! 1. You've said previously that your system is normally up 24/7. To make sure I've understood that statement correctly: you mean that the system is normally on, and you don't use standby, hibernate, or any other power-saving scheme - correct? 2. Without asking you to monitor more closely (...yet!): is it your current understanding/observation that memory usage just slowly creeps up over the seconds and minutes? A dripping tap that slowly but surely leaks ~20 MB per hour, as opposed to static memory usage 99% of the time followed by a burst-increase at [for example] a particular time every hour? 3. Again, without asking you to monitor more closely: is it your current understanding/observation that memory usage starts creeping up from the moment TvS starts? That, as opposed to an issue that only starts after a particular interaction - for example, after the first recording starts or live TV usage? 4. Does this system also run MP? 5. In total how many MP (client/frontend) installations use this instance of TvS? 6. Roughly speaking, what is the usage pattern for the clients? In particular, are some/any always on... or do they generally sit in standby/hibernate unless they're being actively used? I ask the above client-related questions because at this point I honestly can't think of any other purely TvS-driven and "disableable" background tasks. That would only leave us with client interactions (which obviously can't occur when the clients are in standby or not running - hence question 6) and non-disableable tasks such as: [LIST] [*]the recording/scheduler loop ("Is it time to start or stop a recording now?"), which if I recall correctly runs every 15 seconds [*]the power state change monitor ("Does the system want to suspend or resume now?"), which does "stuff" every time Windows notifies us of an event we may or may not care about [*]the tuner detector ("Has a new tuner been connected to the system, or has an existing tuner been disconnected from the system?"), which does "stuff" every time Windows notifies us that "a device connected to the system has changed", and when UPnP devices connect to or disconnect from the network [*]the streaming server, which enables remote clients to stream live TV and recordings [/LIST] All of these are very much core tasks, which is why they can't be disabled. A set of debug-level log files would potentially show how active the power state change monitor, tuner detector, and streaming server are. It's possible - for example - that on your particular system Windows is triggering the tuner detector more often than expected... and therefore the memory usage would be more obvious on your system than any other. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
MediaPortal 1 Talk
Memory leak in TVService
Contact us
RSS
Top
Bottom
