I have been spending some time with a client analyzing the performance of an existing WPF application. We have found a driver-related memory leak and I wanted to share the methodology and findings. The WPF application in question has a bar graph, of sorts, that the user can adjust with the mouse. The bar graph contains a gripper control that the user can click and drag to adjust the height of a bar graph. Users have noticed that performing many bar graph height adjustments consumes memory, eventually...