Running "Screen_Capture_Example" using VS2015, a stack corruption occurs in EnumWindowsProc when the user has a window open with a long title (longer than 128 chars, presumably. In my case the window was a chrome page open to https://github.com/smasherprog/Projects_Setup):
Tested on commit (Edit: pasted wrong commit earlier) https://github.com/smasherprog/screen_capture_lite/commit/5a82135571a9bea0498d48f9a70c6663bd9498fb
Running "Screen_Capture_Example" using VS2015, a stack corruption occurs in
EnumWindowsProc
when the user has a window open with a long title (longer than 128 chars, presumably. In my case the window was a chrome page open to https://github.com/smasherprog/Projects_Setup):buffer
is a 255 char array but w.Name is only 128 chars. Re-organizing the code to:fixes the issue and guards against changes to the size of
w.Name
in the future.Note also that a compilation issue occurred in GDIFrameProcessor.cpp at
ImageRect rect = { 0 };
but presumably this is not a problem for VS2017.