none
32 bit to 64 bit migration issue RRS feed

  • General discussion

  • We have a set a of 32 bit windows services and recently we migrated it to 64 bit server by changing the build option as x64. It is being observed that the performance degraded. Also noticed that the memory utilized by this apps is not released after each execution. We have used disposed method for all database connectivity and in our apps we are using large objects ( which are holding an average of 93168 KB)
    Monday, October 24, 2011 9:37 AM

All replies

  • You can follow the links below to detect .NET application memory leak:

    Detecting .NET application memory leaks

    Memory Leak Detection in .NET

    Memory Leak

     

    Once we have confirmed that there is a memory leak, it's time to investigate the root problem of the memory leak. We will divide our journey to the solution in 3 phases what, how and where.

    • What: - We will first try to investigate what is the type of memory leak, is it a managed memory leak or an unmanaged memory leak.
    • How: - What is really causing the memory leak. Is it the connection object, some kind of file who handle is not closed etc?
    • Where: - Which function / routine or logic is causing the memory leak.

    Paul Zhou [MSFT]
    MSDN Community Support | Feedback to us
    Get or Request Code Sample from Microsoft
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    Tuesday, October 25, 2011 2:06 AM