When history file reaches 500 kb, TCC starts to have problems

#1
After some troubleshooting in a couple of PCs, I found out that if your history file (setting HistFile) reaches about 500 kb (mine was 536.462 bytes), TCC starts to behave a bit erratically.

Symptoms at my pc were:
  • Very slow startup
  • dir and pdir commands would give out corrupted data (usually missing part of the name, or just displaying blanks
  • Folders could not be deleted (they were deleted very easily with cmd.exe though)

The obvious workaround was to delete the history file and start over. This is just a heads up, that there *is* a workaround, and there is also a problem that probably needs to be addressed.

Of course it is entirely possible that there was some problem with my environment, since the results (apart from the very slow startup at least) are not very reproducible in other PCs.
 

rconn

Administrator
Staff member
May 14, 2008
10,572
97
#2
When history file reaches about 500 kb, TCC starts to have problems

> After some troubleshooting in a couple of PCs, I found out that if your
> history file (setting HistFile) reaches about 500 kb (mine was 536.462
> bytes), TCC starts to behave a bit erratically.
>
> Symptoms at my pc were:
> * Very slow startup
> * dir and pdir commands would give out corrupted data (usually missing
> part of the name, or just displaying blanks
> * Folders could not be deleted (they were deleted very easily with
> cmd.exe though)
I can't reproduce any problems with corruption, but you'll definitely (as
expected!) have very slow loads if you try to load a big history file into a
small history buffer. What is the size of your TCC history buffer (OPTION /
Command Line)?

Rex Conn
JP Software
 
#3
When history file reaches about 500 kb, TCC starts to have problems

On Tue, 02 Feb 2010 20:08:19 -0500, gschizas <> wrote:

|After some troubleshooting in a couple of PCs, I found out that if your history file (setting HistFile) reaches about 500 kb (mine was 536.462 bytes), TCC starts to behave a bit erratically.
|
|Symptoms at my pc were:
|* Very slow startup
|* dir and pdir commands would give out corrupted data (usually missing part of the name, or just displaying blanks
|* Folders could not be deleted (they were deleted very easily with cmd.exe though)

I don't know about the other symptoms, but it seems any HistFile would slow down
start/exit because it's read at startup and written as exit. I don't usually
use a HistFile, but I just configured one with option. After the first exit,
the file was 143KB. And subsequent startups took about 4 seconds (compared to
the .06 second to which I am accustomed!).

SHRALIAS does a good job of always making the history available.
--
- Vince
 
May 29, 2008
533
3
Groton, CT
#4
After some troubleshooting in a couple of PCs, I found out that if your history file (setting HistFile) reaches about 500 kb (mine was 536.462 bytes), TCC starts to behave a bit erratically.

Symptoms at my pc were:

...

  • dir and pdir commands would give out corrupted data (usually missing part of the name, or just displaying blanks
...
I've seen that symptom before, but didn't relate it to anything at the time.
Thanks for the clue.
 
#5
I can't reproduce any problems with corruption, but you'll definitely (as
expected!) have very slow loads if you try to load a big history file into a
small history buffer. What is the size of your TCC history buffer (OPTION /
Command Line)?

Rex Conn
JP Software
Unsurprisingly, it's 500000 bytes for commands and 50000 for directory.