1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

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

Discussion in 'Support' started by gschizas, Feb 2, 2010.

  1. gschizas

    Joined:
    May 30, 2008
    Messages:
    81
    Likes Received:
    0
    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.
     
  2. rconn

    rconn Administrator
    Staff Member

    Joined:
    May 14, 2008
    Messages:
    10,040
    Likes Received:
    84
    When history file reaches about 500 kb, TCC starts to have problems

    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. vefatica

    Joined:
    May 20, 2008
    Messages:
    8,078
    Likes Received:
    30
    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
     
  4. dcantor

    Joined:
    May 29, 2008
    Messages:
    508
    Likes Received:
    3
    I've seen that symptom before, but didn't relate it to anything at the time.
    Thanks for the clue.
     
  5. gschizas

    Joined:
    May 30, 2008
    Messages:
    81
    Likes Received:
    0
    Unsurprisingly, it's 500000 bytes for commands and 50000 for directory.
     

Share This Page