k long time ago i made a dos app in C.
it was on a win9x OS and the program checked if there was a command in the system.ini file, if not he would make one else it would skip the adjustment of the .ini file.
By doing this u only had to run this prog once and the rest of the time it would startup when u started windowse 9x.
Now the program opened a file using fopen("blabla.txt","a+");
at the end i didnt fclosed it. And in the program was a while loop (infinite one)
this would make sure that data was constantly being written away to text files..... Now you would aspect an abortion of data transmission and writing when the app is manually closed.... (somekind of an emergency flcose by the OS).
But now what happened the app was closed and it was still writing data to the text file(if you pressed alt-ctrl-delete then it wasnt to see anywhere so it was really really closed of). At a certain moment i noticed that the comp was going awfully slow (that was after 30 after i had closed the app). I went looking to the txt file were data was written to by the prog. And after those 30 sec approx it was already 350 MB big.
This was done in win9x (os didnt gave any warning)
I also did this in xp (without using system.ini) and it gave me an error that there was not enough virtual memory....
Xp did gave a warning BUT none of the tested OS's automatically closed the txt file (that was increasing enormesly with the second)
Isnt this some sort of a leak in stabilty of the system ??