Dimitris Bounias

(note that in the screenshot it just reaches the maximum of the system. With an 1GB image in a 32GB machine it reached 20GB+ of memory usage)

> I think a big reason behind this is the fact that CaPTk **always** loads images as Floats I don't think that float images can make memory usage get to...

Probably all major ones. But it wouldn't really matter anyway, worst case a hidden file and some hidden dirs that do nothing are created.

@Getkablue had this issue, and apparently it is the same for me too. @sarthakpati can you provide some context?

Also [[here]](https://github.com/CBICA/CaPTk/blob/4252d709e691b921a0a9e74e176e8f64bb316466/cmake_modules/Superbuild.cmake#L8): ```cmake IF(MSVC) SET( CMAKE_CONFIGURATION_TYPES "Debug;Release") ELSEIF(UNIX) SET( CMAKE_CONFIGURATION_TYPES "Release") SET( CMAKE_BUILD_TYPE "Release" ) ENDIF() ```

> Ah yes. This is because doing "Debug" build with GCC messes up the entire compilation, for some reason. I have not investigated it in detail, but I remember that...

While the cohort file could help solve mitigate this, I think this issue is about the lack of feedback on why a subject was not included.

> @dboun I am unable to reproduce this on Windows though. It's 3 m.o., I think alex has worked on this, so it might be fixed. Also it might be...

@sarthakpati here you go. I will update with the actual output when it finishes building

@sarthakpati got the whole output. See 'Describe the bug' section