Hmm well I'm not really using any static dynamically allocated variables. Some 3rd party stuff might. Even so without including anything else than <windows.h> it's still giving me the same leaks. Is this something I can ignore then?
Ashaman73: "You are including Engine.h and most likely are linking some static libs here ?"
Does that make any difference even if I'm not including it at all ?
Show differencesHistory of post edits
#3lipsryme
Posted 12 November 2012 - 08:32 AM
Hmm well I'm not really using any static dynamically allocated variables. Some 3rd party stuff might. Even so without including anything else than <windows.h> it's still giving me the same leaks. Is this something I can ignore then?
Ashaman73: "You are including Engine.h and most likely are linking some static libs here ?"
Does that make any difference if I'm not including it at all ?
Ashaman73: "You are including Engine.h and most likely are linking some static libs here ?"
Does that make any difference if I'm not including it at all ?
#2lipsryme
Posted 12 November 2012 - 08:31 AM
Hmm well I'm not really using any static dynamically allocated variables. Some 3rd party stuff might. Even so without including anything else than <windows.h> it's still giving me the same leaks. Is this something I can ignore then?
#1lipsryme
Posted 12 November 2012 - 08:30 AM
Hmm well I'm not really using any static dynamically allocated variables. Some 3rd party stuff might. Even so without including anything else than <windows.h> it's still giving me the same leaks. Is this something I can ignore ?