It seems that DrawFrameControl() creates Font and Brush objects, select them into dc, and doesn't delete them. (according to BoundsChecker messages). Does anyone faced such thing?
R – GDI resource leak in DrawFrameControl
bounds-checkergdi+winapi
bounds-checkergdi+winapi
It seems that DrawFrameControl() creates Font and Brush objects, select them into dc, and doesn't delete them. (according to BoundsChecker messages). Does anyone faced such thing?
Best Answer
I have experienced the same in various OS/CRT Dlls. One of the patterns is where
Since these warnings are definitely not in my code, I would advise on taking them with a grain of salt. Generally what I do is I cleanup any BC warnings that have a reference to my code.
Off topic: BC throws a lot of warnings that a developer can not fix in his code. In stl you will have a myriad of warnings, but most of them are "comparing unrelated pointer". This does not mean that BC is mistakenly throwing them. "Comparing unrelated pointer" in a regular app can be a disaster, but I think the guys that wrote the stl implementation know what they are doing and probably have examined those cases anyway.