Slow Debugger

[Andrew Bullock]

Hi,

I had this problem before I reinstalled Windows XP SP2 (fully patched),
but I cant remember what I had to do to fix it :(

I have a loop which scans every pixel in a series of images. When
compiled it completes 10 images in about 6 seconds, which is acceptable
and as expected.

When i run it through VS it does about 1 frame every 10 seconds.
Obviously it should be slightly slower, but not this bad!
Ive tried turning off "edit and continue" but that doesnt make a difference.
Can anyone offer any other suggestions?

My VS setup is as default, I've not changed any other settings.

Thanks,

Regards

Andrew

[Andrew Bullock]

Willy Denoyette [MVP] wrote:

Scaring, the number of Pages/Sec is extremely high, that means there is
memory trashing (extreme paging).
What's the value of the Memory' 'Committed bytes' and the 'Available Bytes'
counter?
What else do you have running on this box? What are these processes
consuming in terms of committed bytes?

Willy.

Hi, Not sure exactly where to find "committed bytes" but ive shown "%
committed bytes" on perfmon and it only goes up by about 2% when opening
the program, and another 2% for each image it loads.

in the alt-ctrl-del performance window it says:

Commit Charge (K)
Total: 401000 ish
Limit: 2011872
Peak: 499008

Kernel Memory(K)
Total: 59100
Paged: 35032
Nonpaged: 24068

Physical:
Total: 523760
Available: 131010 ish
System Cache: 147024

The only other thing running apart from system things is Thunderbird
in alt-ctrl-del process manager:

devenv.exe is 102Mb
thunderbird is 30meg
explorer 17meg
and loads of 1meg ish things

I usually have 100s of things open and don't experience too much paging lag.

My pagefile is on a seperate logical drive and fixed at 1.45 gig. My Ram
is 2 sticks of separately managed 256Mb. (Mobo is an Abit NF7 s V2) I
have all current platform drivers etc. This is no different to before my
windows reinstall, when i didnt have this problem.

Thanks for helping me out with this, I hope you can help me sort it :)

Regards

Andrew

[Andrew Bullock]

Forgot to say, where it goes up by 2% each time, it starts at 20%.
Andrew

[Andrew Bullock]

Willy Denoyette [MVP] wrote:

Scaring, the number of Pages/Sec is extremely high, that means there is
memory trashing (extreme paging).
What's the value of the Memory' 'Committed bytes' and the 'Available Bytes'
counter?
What else do you have running on this box? What are these processes
consuming in terms of committed bytes?

Willy.

Exactly the same problem occurs on my other pc.

This is a fresh xpsp2 install, default windows settings wrt
memory/paging etc.

Why is it running soooo sloooowww in development, but runs fine when
fully compiled?

:'(
Andrew

[Andrew Bullock]

OK, I've narrowed the problem down to being the same as this:

http://forums.microsoft.com/MSDN/Sho...38755&SiteID=1

It appears to be the .getPixel method which is causing the problems with
the debugger. Ive read the above thread and all its links to everywhere
else.

http://lab.msdn.microsoft.com/produc...ID=FDBK41388#2

Ive done all 3 workarounds but none of them work.

Is there anything else i can try?
Thanks

Andrew

[Willy Denoyette [MVP]]

scroll down in the same list where you found %committed bytes, note that
"Available Bytes" is in the same list ("Memory" Performance Object). Don't
use Taskman, I prefer figures from Perfmon.
As I told you previously, your "pages/sec" counter seems too high, but now I
re-read your previous post I'm not sure what you mean with "is at 100 and
jumps to 90", what I need is the "value" in maximum and average text boxes
(labels). High values during run are an indication that hard paging happens,
and that results in bad performing applications.
So what you should do is inspect the values I gave above and watch them
before program start and while program runs.

Forget about the forum post for the moment, this is not about running in VS
vs. stand-alone.

Willy.

"Andrew Bullock" <an************ *********@ANDnt lworldTHIS.com> wrote in
message news:Mj******** ********@newsfe 3-win.ntli.net...
| Willy Denoyette [MVP] wrote:
| > Scaring, the number of Pages/Sec is extremely high, that means there is
| > memory trashing (extreme paging).
| > What's the value of the Memory' 'Committed bytes' and the 'Available
Bytes'
| > counter?
| > What else do you have running on this box? What are these processes
| > consuming in terms of committed bytes?
| >
| > Willy.
| >
|
|
| Hi, Not sure exactly where to find "committed bytes" but ive shown "%
| committed bytes" on perfmon and it only goes up by about 2% when opening
| the program, and another 2% for each image it loads.
|
| in the alt-ctrl-del performance window it says:
|
| Commit Charge (K)
| Total: 401000 ish
| Limit: 2011872
| Peak: 499008
|
| Kernel Memory(K)
| Total: 59100
| Paged: 35032
| Nonpaged: 24068
|
| Physical:
| Total: 523760
| Available: 131010 ish
| System Cache: 147024
|
| The only other thing running apart from system things is Thunderbird
| in alt-ctrl-del process manager:
|
| devenv.exe is 102Mb
| thunderbird is 30meg
| explorer 17meg
| and loads of 1meg ish things
|
| I usually have 100s of things open and don't experience too much paging
lag.
|
| My pagefile is on a seperate logical drive and fixed at 1.45 gig. My Ram
| is 2 sticks of separately managed 256Mb. (Mobo is an Abit NF7 s V2) I
| have all current platform drivers etc. This is no different to before my
| windows reinstall, when i didnt have this problem.
|
| Thanks for helping me out with this, I hope you can help me sort it :)
|
| Regards
|
| Andrew