Application Server Solutions for Microsoft IIS and ASP.NET
       solutions   products   partners   company   support   downloads         store
ServletExec Self-Help: FAQ
Back to Search >  Back to Search Results

Faq ID 393
Product BlueDragon
Category Debugging
Question How can I troubleshoot a memory leak involving BlueDragon .NET?
Answer
  • Startup the Windows Task Manager and go to the "Processes" tab. Then check the checkbox at the bottom labeled "Show processes from all users". Then click the column header for the column named "Name" (to sort the processes alphabetically by name). Then look for processes named "w3wp.exe" At the top of the Task Manager window is a menu from which you may navigate as follows:
    View - Select Columns...
    From there you can customize the list of columns to include a column for the PID.
    Note the PID of your w3wp.exe process.
    If you have more than 1 w3wp process running you may need to turn off the App Pool that BD .NET is using and take note of which w3wp PIDs remain. Then turn it back on and take note of the newly listed w3wp.exe PID (that would be the one in which BD.NET is running).
    Be sure to configure that App Pool to never recycle itself.
    Then periodically (every day or so) take note of the memory usage of that PID.
    We've done this before for 8 consecutive days in a non-memory-leaking setup. Data collected during the first 7 days suggested an upward trend, but data on the 8th day confirmed that there was no leak. So you may need to watch this across many days to get the truth for your own system. It just depends on how often the .NET garbage collector runs on your system. The highest value we saw in our trivial test was 86,416 Kilobytes which is tiny and well within acceptable memory usage for an IIS Application Pool
  • IF you can confirm that the memory *trend* of your PID across many days and or weeks is always up (and definitely not down) then please use this information to obtain a memory dump of the running Application Pool process (use the PID) and then please send us that dump.
    We are happy to analyze it here.

    Please know that if the PID memory usage trend is *not* upwards then analyzing a dump would not be useful. The process would need to be in a clear state of "heading towards OutOfMemory" so that the problem could be clearly picked out from the dump. In fact the more "out of balance" the process is... the better it would be for analysis purposes.
  • Another tool that could be used to gather data about a running Application Pool process (w3wp.exe) is the Microsoft Debug Diagnostic Tool v1.1. It can be used to both generate and analyze a dump of most any Windows process.



   
company media information terms of use privacy policy contact us