Timer fires before detectClipboard completes (startup race on first statusCheck) #26

New issue

Closed

opened 2026-05-19 04:25:05 +00:00 by vybe · 2 comments

vybe commented

2026-05-19 04:25:05 +00:00

Collaborator

Problem

The 5-second status timer is declared with running: true while detectClipboard is started in Component.onCompleted. Both can execute near-simultaneously on startup, so the first statusCheck may run before root.clipboardCmd has been populated by the detection process.

Impact

The widget performs one unnecessary or slightly early status poll on every load. The race is benign but wastes a process invocation and can produce a transient state where clipboard operations are not yet configured.

## Problem The 5-second status timer is declared with `running: true` while `detectClipboard` is started in `Component.onCompleted`. Both can execute near-simultaneously on startup, so the first `statusCheck` may run before `root.clipboardCmd` has been populated by the detection process. ## Impact The widget performs one unnecessary or slightly early status poll on every load. The race is benign but wastes a process invocation and can produce a transient state where clipboard operations are not yet configured.