I am working on a program that, at the moment, is about 1500 lines of code. As it is quite complicated, in order to test it, I run it very often, but only very very rarely I arrive to the end, because I always brutally close the window when I arrive to the point I am testing. I have done this at least thousands times.
well, yesterday I found my 220 Gb of unit C completely full. Adding the occupated space of the directories in C, the amount should be 54 gb, but the 220 Gb were inexplicably full anyway. Furthermore, Windows 10 was about 24 Gb, that is normal. The problem seemed to be thousands of "system files" in \windows\temp, only visible enabling the visibility of hidden files, that occupied almost entirely C. But it is quite weird that the directory "Windows" seemed to be only 24 Gb.
My code creates 59 images and, at the end, I _FREEMAGE all of them, but, as I said, I always interrupt the program before it arrives to the _FREEMAGE sequence.
So, I ask:
- In general, are there potential physical memory problems interrupting program before the end?
- In particular, are there potential physical memory problems interrupting or ending program without _FREEIMAGE the images created?
I believed that not _FREEIMAG(ing) was only a matter of RAM.
