debugging slows down other actions

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • tshad

    debugging slows down other actions

    I am using VS 2005 and find that if I am debugging my program and am still
    in debug mode, certain functions slow down.

    For example, if I tracing through some of my code and haven't stopped
    debugging and try to open a Windows Explorer window, it will take close to a
    minute for the window to open up (using the windows/e combination keys).
    After the window opens, I can open up another window and it will open right
    away. Until I step to another line - then it is slow again the next time I
    try to open a window.

    Also, if in debug mode and I try to open the window and it doesn't open, I
    can stop debugging and it will open immediatly.

    Why does this happen?

    It doesn't happen with everything. IE seems to be unaffected.

    Thanks,

    Tom


  • Fredo

    #2
    Re: debugging slows down other actions

    VS.NET takes up a lot of memory. Debugging an app takes even more. I suspect
    the delay is caused by page faults. You can verify this by opening task
    manager, click on View/Select Columns... and check the Page Faults Delta
    item.

    Then sort on PF Delta in the list and then perform the steps. I suspect
    you'll see big numbers popping up here.

    Most likely you just need more ram.


    "tshad" <tshad@dslextre me.comwrote in message
    news:ezuwoI3kIH A.3780@TK2MSFTN GP06.phx.gbl...
    >I am using VS 2005 and find that if I am debugging my program and am still
    >in debug mode, certain functions slow down.
    >
    For example, if I tracing through some of my code and haven't stopped
    debugging and try to open a Windows Explorer window, it will take close to
    a minute for the window to open up (using the windows/e combination keys).
    After the window opens, I can open up another window and it will open
    right away. Until I step to another line - then it is slow again the next
    time I try to open a window.
    >
    Also, if in debug mode and I try to open the window and it doesn't open, I
    can stop debugging and it will open immediatly.
    >
    Why does this happen?
    >
    It doesn't happen with everything. IE seems to be unaffected.
    >
    Thanks,
    >
    Tom
    >

    Comment

    • tshad

      #3
      Re: debugging slows down other actions


      "Fredo" <fredo@hotmail. comwrote in message
      news:uJOdnRj4EM jhzG_anZ2dnUVZ_ hisnZ2d@giganew s.com...
      VS.NET takes up a lot of memory. Debugging an app takes even more. I
      suspect the delay is caused by page faults. You can verify this by opening
      task manager, click on View/Select Columns... and check the Page Faults
      Delta item.
      >
      Then sort on PF Delta in the list and then perform the steps. I suspect
      you'll see big numbers popping up here.
      >
      Most likely you just need more ram.
      Could be right.

      I do see page faults happening when I do it.

      But I have a Pentium 4 3.00 GHz with 2GB of RAM.

      Thanks,

      Tom
      >
      >
      "tshad" <tshad@dslextre me.comwrote in message
      news:ezuwoI3kIH A.3780@TK2MSFTN GP06.phx.gbl...
      >>I am using VS 2005 and find that if I am debugging my program and am still
      >>in debug mode, certain functions slow down.
      >>
      >For example, if I tracing through some of my code and haven't stopped
      >debugging and try to open a Windows Explorer window, it will take close
      >to a minute for the window to open up (using the windows/e combination
      >keys). After the window opens, I can open up another window and it will
      >open right away. Until I step to another line - then it is slow again
      >the next time I try to open a window.
      >>
      >Also, if in debug mode and I try to open the window and it doesn't open,
      >I can stop debugging and it will open immediatly.
      >>
      >Why does this happen?
      >>
      >It doesn't happen with everything. IE seems to be unaffected.
      >>
      >Thanks,
      >>
      >Tom
      >>
      >
      >

      Comment

      • Peter Duniho

        #4
        Re: debugging slows down other actions

        On Tue, 01 Apr 2008 11:03:04 -0700, tshad <tshad@dslextre me.comwrote:
        "Fredo" <fredo@hotmail. comwrote in message
        news:uJOdnRj4EM jhzG_anZ2dnUVZ_ hisnZ2d@giganew s.com...
        >VS.NET takes up a lot of memory. Debugging an app takes even more. I
        >suspect the delay is caused by page faults. You can verify this by
        >opening
        >task manager, click on View/Select Columns... and check the Page Faults
        >Delta item.
        >>
        >Then sort on PF Delta in the list and then perform the steps. I suspect
        >you'll see big numbers popping up here.
        >>
        >Most likely you just need more ram.
        >
        Could be right.
        >
        I do see page faults happening when I do it.
        Keep in mind that page faults are not in and of themselves bad. They
        happen all the time even under normal memory situations.

        What you want to watch out for are a very large number of page faults over
        a short period of time, with a high correlation to disk i/o (with many
        disks, you can even hear the side-effect of the i/o...they make noise when
        the head's seeking back and forth as the i/o happens).
        But I have a Pentium 4 3.00 GHz with 2GB of RAM.
        2GB of RAM is sometimes a very large amount of memory and sometimes is not
        nearly enough. It depends a lot on what OS you're using, what other
        software is running, and what that other software is actually doing.

        Pete

        Comment

        • Willy Denoyette [MVP]

          #5
          Re: debugging slows down other actions

          "tshad" <tshad@dslextre me.comwrote in message
          news:ezuwoI3kIH A.3780@TK2MSFTN GP06.phx.gbl...
          >I am using VS 2005 and find that if I am debugging my program and am still
          >in debug mode, certain functions slow down.
          >
          For example, if I tracing through some of my code and haven't stopped
          debugging and try to open a Windows Explorer window, it will take close to
          a minute for the window to open up (using the windows/e combination keys).
          After the window opens, I can open up another window and it will open
          right away. Until I step to another line - then it is slow again the next
          time I try to open a window.
          >
          Also, if in debug mode and I try to open the window and it doesn't open, I
          can stop debugging and it will open immediatly.
          >
          Why does this happen?
          >
          It doesn't happen with everything. IE seems to be unaffected.
          >
          Thanks,
          >
          Tom
          >

          Have you install SP1 for VS2005, this one did solve a number of debugger
          slowdown issues.

          Willy.

          Comment

          • tshad

            #6
            Re: debugging slows down other actions


            "Willy Denoyette [MVP]" <willy.denoyett e@telenet.bewro te in message
            news:%23NmRtmDl IHA.3780@TK2MSF TNGP06.phx.gbl. ..
            "tshad" <tshad@dslextre me.comwrote in message
            news:ezuwoI3kIH A.3780@TK2MSFTN GP06.phx.gbl...
            >>I am using VS 2005 and find that if I am debugging my program and am still
            >>in debug mode, certain functions slow down.
            >>
            >For example, if I tracing through some of my code and haven't stopped
            >debugging and try to open a Windows Explorer window, it will take close
            >to a minute for the window to open up (using the windows/e combination
            >keys). After the window opens, I can open up another window and it will
            >open right away. Until I step to another line - then it is slow again
            >the next time I try to open a window.
            >>
            >Also, if in debug mode and I try to open the window and it doesn't open,
            >I can stop debugging and it will open immediatly.
            >>
            >Why does this happen?
            >>
            >It doesn't happen with everything. IE seems to be unaffected.
            >>
            >Thanks,
            >>
            >Tom
            >>
            >
            >
            Have you install SP1 for VS2005, this one did solve a number of debugger
            slowdown issues.
            Doesn't appear so.

            I have version 8.0.50727.762 (SP.050727-7600) so that may be my problem.

            I will try that.

            Thanks,

            Tom
            >
            Willy.
            >

            Comment

            Working...