hluk/CopyQ

CopyQ Creates a Blank Unclosable Window, Subsequently opens Second Window

Open

#1,228 opened on Oct 7, 2019

View on GitHub
 (11 comments) (0 reactions) (0 assignees)C++ (7,372 stars) (419 forks)batch import
Windowsbughelp wanted

Description

Sometimes when I try to open CopyQ to select an entry it opens a completely Blank & Unclosable Window. Trying again successfully opens a second Window.

I do not know how to reproduce this, perhaps click too many times or too fast on tray icon. Its happened enough times that it can't be too hard to do.

I don't think the log shows anything, will look at it closer next time, but no events logged today and all options ticked.

The only way to close the first blank window is to kill the process.

CopyQ 2nd uncloseable blank Window

Environmental Information That should be displayed in the About Box

CopyQ Version: v3.8.0
Windows 10 64 bit
(any other info you need)

Contributor guide

Tech stack
cpp
Domain
desktop
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
C++Qtevent handlingdebugging techniques
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
This bug manifests intermittently when clicking the tray icon rapidly or multiple times. Investigate the tray icon click event handling in CopyQ's source code. Check whether the window creation logic ensures that only one main window is created and that duplicate click events are debounced. Look at files like 'src/gui/trayicon.cpp' and 'src/gui/mainwindow.cpp' for event handling. Also consider if there is a race condition in window initialization. Reproduce the issue by simulating rapid clicks on the tray icon in a debug build and examine the log output. The maintainer may need to clarify expected behavior.