After researching other posts in the Support Forum, it appears that the problem is the level of activity (enabling and disabling symbols, getting data from multiple timeframes), and my liberal use of the Print command. At the end of a normal day, my trace file is about 10GB and log file is 2GB, and lines printed by the program or by NT activity total about 5,000 lines.
So, I'll admit it, the memory problem is not caused by NT but by me because logs and traces are stored in memory. I'll work on eliminating the unnecessary prints, but most of it is very useful for my post-trade analysis.
The suggestion is: create a NinjaScript command to flush the log and trace data from memory. You don't have to get rid of the data, just archive it and remove it from memory when this command is called. The consequence might be that my output window will go blank or I might have to deal with multiple trace files for the same day, but that's not a huge inconvenience, especially if my program is in charge of deciding when to do the flush.
Comment