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: 1283398" data-attributes="member: 82144"><p>In short, you'd need to grab the code from Github. Simplest way to do that is to get just the 1.27 release code from here:</p><p>[URL unfurl="true"]https://github.com/MediaPortal/MediaPortal-1/archive/Release_1.27.0.zip[/URL]</p><p></p><p>Then to attach to the process you'd use Visual Studio 2019 Community Edition:</p><p>[URL unfurl="true"]https://visualstudio.microsoft.com/vs/community/[/URL]</p><p>[URL unfurl="true"]https://docs.microsoft.com/en-us/visualstudio/debugger/attach-to-running-processes-with-the-visual-studio-debugger?view=vs-2019[/URL]</p><p></p><p>Alternatively, a quick Internet search suggests something like this product could be useful:</p><p>[URL unfurl="true"]https://www.red-gate.com/products/dotnet-development/ants-memory-profiler/[/URL]</p><p></p><p></p><p>.NET processes don't manually acquire and release memory. Memory management is all done behind the scenes by the .NET garbage collector. For that reason it isn't really practical to add more logging.</p><p></p><p>Some information about how memory management works with .NET applications:</p><p>[URL unfurl="true"]https://docs.microsoft.com/en-us/dotnet/standard/garbage-collection/[/URL]</p></blockquote><p></p>
[QUOTE="mm1352000, post: 1283398, member: 82144"] In short, you'd need to grab the code from Github. Simplest way to do that is to get just the 1.27 release code from here: [URL unfurl="true"]https://github.com/MediaPortal/MediaPortal-1/archive/Release_1.27.0.zip[/URL] Then to attach to the process you'd use Visual Studio 2019 Community Edition: [URL unfurl="true"]https://visualstudio.microsoft.com/vs/community/[/URL] [URL unfurl="true"]https://docs.microsoft.com/en-us/visualstudio/debugger/attach-to-running-processes-with-the-visual-studio-debugger?view=vs-2019[/URL] Alternatively, a quick Internet search suggests something like this product could be useful: [URL unfurl="true"]https://www.red-gate.com/products/dotnet-development/ants-memory-profiler/[/URL] .NET processes don't manually acquire and release memory. Memory management is all done behind the scenes by the .NET garbage collector. For that reason it isn't really practical to add more logging. Some information about how memory management works with .NET applications: [URL unfurl="true"]https://docs.microsoft.com/en-us/dotnet/standard/garbage-collection/[/URL] [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
MediaPortal 1 Talk
Memory leak in TVService
Contact us
RSS
Top
Bottom