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: 1283372" data-attributes="member: 82144"><p>Thanks for the log files!</p><p></p><p>In short, there's nothing that stands out as concerning.</p><p></p><p>Putting aside the service start and stop stuff, the most common entries in the main log files (TVService.*.log) during your test are related to the tuner detector. In fact there's almost nothing else. The tuner detector does seem to run more often than is absolutely necessary, On average, perhaps every half hour or so, but it appears to be irregular/unpredictable. In an ideal world the detector would only run when a tuner is connected or disconnected; in the real world it runs when Windows reports a device change event, which may well be entirely unrelated to tuners. Cutting to the chase, in my opinion it's unlikely that the detector is causing a memory leak on your system because:</p><ol> <li data-xf-list-type="ol">I've seen the "running more often than absolutely necessary" behaviour before, including on my own system. In my experience it is normal and has never been indicative of a problem of any kind.</li> <li data-xf-list-type="ol">As previously mentioned, the detector appears to run irregularly/sporadically/randomly. This is not at all consistent with a slow and steady 20 MB per hour memory leak. If it were the detector causing a leak, I'd expect memory usage to jump significantly every time it runs.</li> <li data-xf-list-type="ol">There are periods in your log files - for example: between 9 PM on the 12th and 9 AM on the 13th - during which the tuner detector doesn't run at all. Again, this is not at all consistent with a continuous memory leak.</li> </ol><p></p><p>Honestly, I'm not to sure where to go from here. Once again my hope for an obvious issue with an obvious cause have been dashed.</p><p></p><p>Given that the log files aren't showing anything much, really the only other way to determine what's going on would be to use developer tools to attach to the TvS process and "debug" it. However, this isn't particularly straightforward. Are you a developer? ...or do you happen to have experience doing that sort of thing?</p></blockquote><p></p>
[QUOTE="mm1352000, post: 1283372, member: 82144"] Thanks for the log files! In short, there's nothing that stands out as concerning. Putting aside the service start and stop stuff, the most common entries in the main log files (TVService.*.log) during your test are related to the tuner detector. In fact there's almost nothing else. The tuner detector does seem to run more often than is absolutely necessary, On average, perhaps every half hour or so, but it appears to be irregular/unpredictable. In an ideal world the detector would only run when a tuner is connected or disconnected; in the real world it runs when Windows reports a device change event, which may well be entirely unrelated to tuners. Cutting to the chase, in my opinion it's unlikely that the detector is causing a memory leak on your system because: [LIST=1] [*]I've seen the "running more often than absolutely necessary" behaviour before, including on my own system. In my experience it is normal and has never been indicative of a problem of any kind. [*]As previously mentioned, the detector appears to run irregularly/sporadically/randomly. This is not at all consistent with a slow and steady 20 MB per hour memory leak. If it were the detector causing a leak, I'd expect memory usage to jump significantly every time it runs. [*]There are periods in your log files - for example: between 9 PM on the 12th and 9 AM on the 13th - during which the tuner detector doesn't run at all. Again, this is not at all consistent with a continuous memory leak. [/LIST] Honestly, I'm not to sure where to go from here. Once again my hope for an obvious issue with an obvious cause have been dashed. Given that the log files aren't showing anything much, really the only other way to determine what's going on would be to use developer tools to attach to the TvS process and "debug" it. However, this isn't particularly straightforward. Are you a developer? ...or do you happen to have experience doing that sort of thing? [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
MediaPortal 1 Talk
Memory leak in TVService
Contact us
RSS
Top
Bottom