TeraTerm sometimes crashes if SSH times out and you try again using "File > New Connection" instead of closing and reopening the window.
Alert box text:
eax=00000000 ebx=00414850 ecx=00000000 edx=126CFEF0
esi=126CFEF0 edi=00000000
ebp=00000000 esp=0018FBE0 eip=1252B8F6 efl=0010246
cs=0023 ss=002B ds=002B es=002B fs=0053 gs=002B
Exception: ACCESS_VIOLATION
Tera Term
TeraTerm crashes if you use it to SSH to a Cisco or Juniper router via Ipv4, and you don't enter a password in time, and the remote device disconnects, and you go back to the same window, then go to File > "New Connection" (i.e. if you attempt to re-use an inactive window.)
Environment: Windows 7 Enterprise Service Pack 1 (64-bit) Virtual (VMware-based) desktop environment (VDI) (Horizon agent version 6.2) with Intel Xeon CPU ES5-2698 v4 @2.2 gigahertz (2 processors) Tera Term version 4.101 (SVN #7288) (Nov 30 2018 build) Includes Tera Term Pro version 2.3. Optional package installed: Repeating command (to keep SSH sessions alive)
Steps to reproduce: SSH to a Cisco or Juniper router. Use "plain-password" authentication but wait for the device to timeout (that is, you don't add the SSH key to your "known hosts" list and don't enter a password). Then wait a few more minutes, then go to File > New Connection and try to SSH to the same (or different) device.
Expected result: The window is re-used for the new connection.
Actual result: An alert box pops up.
Workaround: Close the window and open a new one instead of using "File > New connection" in the inactive window.