I have a strange situation on one computer (32 bit, XP PRO):
I have a .cmd procedure which (in short) reads an input .txt file (with 20000+ records (delimited), based on a field in this file makes a search (findstr) in another file (or set of file, for example: folder\*.txt). And based on that result it writes some new data to a new file.
Looks like this .cmd causes my computer to have a memory leak - after few times I run this .cmd no new processes can be created, no network connections cannot be established (I cannot access internet, I cannot access maped drives etc.)
I suspect findstr might be the reason.
Any ideas how to find the cause/repair this etc.?
This test triggered the problems in 30 minutes (2GB RAM, closed all other programs). Folder _TXT contains ~60 TXT files. (all of them contain ~25000 records)
Code: Select all
>nul (findstr /c:ASDFASDF _TXT\*.*)
Anyone can confirm this?
P.S. I will take the test on another computer.