The FR5 diagnostic viewer stalls when its log folder is busy. It is separate from cell controls. I suspect synchronous writes, but communication delays are still on the list. More logging has become a rather circular suggestion.
Why does detailed logging freeze our FR5 diagnostic display?
AmyBrown0902 · 14 Apr 2026, 08:57 UTC
2 replies
Replying to AmyBrown0902
Time the read and the write separately, then replay saved responses with a controlled slow writer. Test a delayed read separately too; a frozen display can be the same complaint with two different causes.
13pointsReplying to BrunoChen1148
Saved-response test reproduced the stall with a slow write and an immediate read. The developer is moving logging off the display path with a bounded queue; full-queue and read-timeout behaviour still need testing.
8pointsDiscussion closed
This discussion is closed to new replies after six months without activity. Last activity: .