Menu
▾
▴
1 Attachments
#214 SyncTERM freezes
Hello! After starting SyncTERM, I press the "down arrow" key and hold this key, SyncTERM starts moving through the list of BBS and freezes. You can see this in the video. SyncTERM for Win64 recompiled Fri Jan 02 2026 08:04:40, from http://www.syncterm.net
Discussion
Anonymous
Hrm, I can't seem to reproduce this on my Windows system. I notice in the video that there's some mouse usage at the beginning... is this required to reproduce it?
Windows 10 x64, no mouse required. In the list of active BBSs, press and hold the down arrow key. The selection will move downwards, and SyncTERM will eventually freeze. If playback fails, return to the very top of the BBS list and press and hold the down arrow key again.
Hrm, does it always freeze on the same entry? Or is it somewhat arbitrary?
In various entries. The bug appeared in commit 151af2c0 (151af2c066100dff02f067129fee91815587aa1a); the bug didn't exist before this commit.
Hmm, I found another bug that appeared in commit 93d46cb6 (93d46cb6ef33f1a0613aa5f57a0e87256ddd0f57), when you press the down arrow key, it does not jump to the top of the BBS list, instead it jumps as shown in the video.
These both look like issues that should have been fixed with
f1732d3cfd0399cda4cf82e1d40bdd26e46d7d94… especially the second one.Before commit 93d46cb6 (93d46cb6ef33f1a0613aa5f57a0e87256ddd0f57) there were no problems with long pressing the down arrow key...
Yes, but after commit
151af2c066100dff02f067129fee91815587aa1a, there should not have been the "jumping" issue (where a down-arrow is apparently interpreted as aPkeypress).Working blindly on the assumption that the hang is related to potential ciolib concurrency issues, I've added a mutex and rebuild. Please confirm if this is fixed in builds at or after Sat Jan 03 2026 20:00:26.
Yes, this bug is fixed now, thanks! But I just noticed that if you hold down the up arrow key for a long time, the SyncTERM freezes. I think you need to fix it for the up arrow key as well.
Hrm, they're the same code path, so it's likely not actually fixed for down arrow either, just less likely to occur.