none
Application freeze RRS feed

  • Question

  • Hi experts,

    we have a .Net 4 application (Windows.Forms, Infragistics controls, Multithreading, Sql Server) that freezes at runtime after some user actions in production. The freeze is not repeatable, so we have to wait until the freeze happens und we can start analyzing.

    What is the best way to find the cause for this problem, what can we do to analyse a freezed application in production environment?

    We have already installed a debug version, started debugging -> break but we have not found any clue.

    Any hints where to search would be veeeeeery valuable!

    Does anybody have experience with this case?

    Thanks a lot in advance

    Ulrich

    Tuesday, May 8, 2012 9:46 AM

Answers

  • Hi Ulrich,

    Welcome to the MSDN Forum.

    Based on my experience, it may caused by your network.

    When you try to communicate others in your network in UI thread, and when the network is very busy at a special point, the application will be freezed and waiting the response.

    Another possibility:

    You access a SQL table in UI thread, and the table is locked and your operation is been blocked, wait the table is unlocked. At this time, your application should be freezed.

    In all, your UI thread is waiting some other operation outside of your application, so you are hard to debug it.

    So, you may need to check all your UI threads to find which operations may cause this scenario.

    Best regards,


    Mike Feng
    MSDN Community Support | Feedback to us
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    Wednesday, May 9, 2012 12:21 PM
    Moderator
  • Hi Ulrich,

    Please check the size of data. If it is too use, then also it will cause your application to freeze. If possible, use BackgroundWorker thread or try to access data in small small chunks.


    Regards, http://shwetamannjain.blogspot.com

    Wednesday, May 9, 2012 12:29 PM

All replies

  • Hi Ulrich,

    Welcome to the MSDN Forum.

    Based on my experience, it may caused by your network.

    When you try to communicate others in your network in UI thread, and when the network is very busy at a special point, the application will be freezed and waiting the response.

    Another possibility:

    You access a SQL table in UI thread, and the table is locked and your operation is been blocked, wait the table is unlocked. At this time, your application should be freezed.

    In all, your UI thread is waiting some other operation outside of your application, so you are hard to debug it.

    So, you may need to check all your UI threads to find which operations may cause this scenario.

    Best regards,


    Mike Feng
    MSDN Community Support | Feedback to us
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    Wednesday, May 9, 2012 12:21 PM
    Moderator
  • Hi Ulrich,

    Please check the size of data. If it is too use, then also it will cause your application to freeze. If possible, use BackgroundWorker thread or try to access data in small small chunks.


    Regards, http://shwetamannjain.blogspot.com

    Wednesday, May 9, 2012 12:29 PM
  • Hi Mike,

    thanks a lot for your hints.

    Are there any recommended tools to find the problem?

    Best regards

    Ulrich

    Wednesday, May 9, 2012 9:45 PM
  • Hi Shweta,

    thanks a lot for your hints.

    Are there any recommended tools to find the problem?

    Best regards

    Ulrich

    Wednesday, May 9, 2012 9:46 PM
  • Hi Ulrich,

    Please try the Performance tool in VS:

    Best regards,


    Mike Feng
    MSDN Community Support | Feedback to us
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    Thursday, May 10, 2012 3:45 AM
    Moderator