[Bug]: ARB download blocks the GUI thread #2

New Issue

2026-04-17T11:28:49Z

tgohle commented

2026-04-17 11:28:49 +00:00

Problem

ARB download currently performs a blocking socket receive loop in the GUI thread.

Current code

chunk = self.i.sock.recv(min(65536, need))

This happens inside on_arb_download().

Why this is a bug

Large ARB downloads can freeze the GUI until the transfer finishes or times out.

That is bad behaviour for a desktop instrument-control tool, especially if the user expects the interface to stay responsive during waveform transfer.

Fix approach

Move ARB download into a dedicated QThread worker, following the same general pattern already used for ScreenshotWorker.

The GUI thread should only launch the worker and handle completion, logging, and file saving through a signal.

Status

Local fix already implemented in the current v0.2 working copy.
Still needs commit, push, and hardware verification before closing.

### Problem ARB download currently performs a blocking socket receive loop in the GUI thread. ### Current code ```python chunk = self.i.sock.recv(min(65536, need)) ``` This happens inside `on_arb_download()`. ### Why this is a bug Large ARB downloads can freeze the GUI until the transfer finishes or times out. That is bad behaviour for a desktop instrument-control tool, especially if the user expects the interface to stay responsive during waveform transfer. ### Fix approach Move ARB download into a dedicated `QThread` worker, following the same general pattern already used for `ScreenshotWorker`. The GUI thread should only launch the worker and handle completion, logging, and file saving through a signal. ### Status Local fix already implemented in the current v0.2 working copy. Still needs commit, push, and hardware verification before closing.

tgohle added the area/arb

labels 2026-04-17 11:38:33 +00:00

tgohle added this to the v0.2.0 - first bugfix round finished milestone 2026-04-17 12:08:10 +00:00