I have been developing one large and complex WPF application for 13 months now, all is going well and especially tonight as I now have some sort of clue or hint to what I have been seing now for quite some time. Here is the rundown.
1) Running on i5 processor with 4GB RAM and Windows 7
2) The application was developed all in .Net 4.0, WPF C#.
3) It is heavily GUI intensive and also uses Entity Framework Detached for Database Access.
4) Is multi-threaded / multi-tasking.
I am a nutcase when it comes to testing. Since my graphical application heavily depends upon performance and determinsm (please somebody don't start with the C++ vs .Net on here) and has been performing great FOR THE MOST PART. Every once in
a while, I see that the application runs into the weeds for 5 or 6 seconds and the interface is unresponsive. I have this thing tuned finely too. Well now toward the end of development I have finally had to face that bug so to speak. I can
force it by clicking spastically on my buttons causing an event storm and making the system update the GUI.
SO! Great start, I can now cause the problem on a regular basis (for you youngsters that is actually a good thing)! Alright, so I start with the easiest investigative tool, CNTRL - ALT - DEL into Windows 7 Performance Monitor. As you can
View Complete Post