hluk/CopyQ

Error issued at system shutdown

Open

#1,249 opened on Nov 4, 2019

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

Description

When shutting down Windows, CopyQ issues the following message:

Command “copyq onExit”
Error: Process crashed

Upon looking at CopyQ's log, I see

Note [2019-11-01 20:03:38.534] <Server-2228>: Command “copyq --clipboard-access monitorClipboard”
Note [2019-11-01 20:03:38.534] <Server-2228>:    Error: Process crashed
Note [2019-11-01 20:03:38.534] <Server-2228>:    1. copyq --clipboard-access monitorClipboard
Note [2019-11-01 20:09:47.941] <Server-2208>: Command “copyq --clipboard-access monitorClipboard”
Note [2019-11-01 20:09:47.941] <Server-2208>:    Error: Process crashed
Note [2019-11-01 20:09:47.941] <Server-2208>:    1. copyq --clipboard-access monitorClipboard
Note [2019-11-01 20:09:48.003] <Server-2208>: Command “copyq --clipboard-access monitorClipboard”
Note [2019-11-01 20:09:48.003] <Server-2208>:    Error: Process crashed
Note [2019-11-01 20:09:48.003] <Server-2208>:    1. copyq --clipboard-access monitorClipboard
Note [2019-11-01 20:09:50.172] <Server-2208>: Command “copyq onExit”
Note [2019-11-01 20:09:50.172] <Server-2208>:    Error: Process crashed
Note [2019-11-01 20:09:50.172] <Server-2208>:    1. copyq onExit
Note [2019-11-01 20:09:50.218] <Server-2208>: Command “copyq onExit”
Note [2019-11-01 20:09:50.218] <Server-2208>:    Error: Process crashed
Note [2019-11-01 20:09:50.218] <Server-2208>:    1. copyq onExit

The system was turned off and restarted twice during that time.

It looks like one error might be happening when Windows starts (CopyQ is run on startup), and another when Windows is shut down.

I do have CopyQ syncing with an empty sync path to clear the CopyQ data between reboots (see https://github.com/hluk/CopyQ/issues/1063).

Version, OS and Environment

  • CopyQ Version v3.9.2
  • Windows 7 64-bit

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.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 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++QtWindows shutdown process
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
Investigate the onExit command and monitorClipboard process. Check how CopyQ handles system shutdown signals on Windows. Look at the logs to identify the point of crash. The issue might be related to the order of process termination. Consider testing with an empty sync path as mentioned. Relevant files likely include source files handling clipboard monitoring and exit commands.