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 · 2026年4月14日 08:57 UTC
主帖中文翻译暂不可用，以下显示英文原文；回复保留原文。 查看英文原文
2 条回复
回复 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.
13分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.
8分讨论已关闭
此讨论已连续六个月没有活动，现已关闭新回复。 最后活动： .