CopyQ crashed randomly

[ghost]

After new update, copyq crashed randomly and shown up a message box.
Not really a matter to me but I think I should report it here.

Command “copyq: if (monitoring()) {updateTitle()}”
Error: Process crashed

---
copyq: if (monitoring()) {updateTitle()}

---

$ copyq --version
CopyQ Clipboard Manager v2.5.0 ([email protected])
Built with: Qt 5.5.1, LibQxt 0.7.0

My system: Arch Linux 64-bit with bspwm (not using any DE).

Hope it helps.

[hluk]

Does the main application stay running in tray? It seems that only the command crashes for some reason.

Is that version installed from AUR? Did you try reinstalling?

Is the result same if following is run from Action dialog F5?

copyq: if (monitoring()) {updateTitle()}

[ghost]

1. Yes, it's still running on system tray.
2. Perhaps yes, or no. It's the binary version from antergos repo, but both antergos repo and aur holding the same ver atm (2.5.0-1) so I don't think it would make difference.
3. Strange, it runs flawlessly.

I've been using copyq for a long time on both arch and windows, but this is the first time I see this error message. I'll tell if it happens again in this ver with (maybe) more details.

[helloworld1]

I still have the same issue in copyq 2.7.0 from AUR.
copyq --version ~
CopyQ Clipboard Manager v2.7.0 ([email protected])
Built with: Qt 5.6.0, LibQxt 0.7.0

I am using i3wm.

[hluk]

@helloworld1 Is this related? Can you provide more info?

I fixed some crashes when running commands. The fix will be in next version. You can try copyq-git from AUR (it should be stable).

[Brottweiler]

I get this error every once in a while, randomly it seems. I have no idea what causes it.

When I get it, I just need to copy what I tried to copy again, and then it's fine. CopyQ never actually crashes, I just get the message and the copy fails.

[hluk]

@Brottweiler Definitely upgrade to version 2.7.1 if you can. I fixed some issues with scripting that look exactly like this (script runs in separate process and crashes after it destroys communication socket).

[Brottweiler]

I should've mentioned this, but I am running 2.7.1.

[hluk]

This could be a problem with how Qt handles destroying sockets :/.

Can you provide output of copyq --version.

[Brottweiler]

CopyQ Clipboard Manager v2.7.1 ([email protected])
Built with: Qt 5.7.0, LibQxt 0.7.0

[hluk]

I've been using CopyQ with Qt 5.7.0 for few days without crashes.

Can you provide information through coredumpctl? List available core dumps for recent crashes with coredumpctl and print more info about last copyq process crash with coredumpctl info <PID>.

[Brottweiler]

           PID: 8185 (copyq)
           UID: 1000 (brott)
           GID: 1000 (brott)
        Signal: 11 (SEGV)
     Timestamp: Sun 2016-07-24 12:29:51 CEST (5h 41min ago)
  Command Line: /usr/bin/copyq eval --  if (monitoring()) {updateTitle('')}
    Executable: /usr/bin/copyq
 Control Group: /
         Slice: -.slice
       Boot ID: 94e60ed51e74425daa1b5e7c3d0f84f2
    Machine ID: 6465c58d0fda4d76bca856d45cec1a01
      Hostname: noname
      Coredump: /var/lib/systemd/coredump/core.copyq.1000.94e60ed51e74425daa1b5e7c3d0f84f2.8185.1469356191000000000000.lz4
       Message: Process 8185 (copyq) of user 1000 dumped core.

                Stack trace of thread 8186:
                #0  0x00007fcfe1fe2c33 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5)
                #1  0x00007fcfe1fe53fd _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt5Core.so.5)
                #2  0x00007fcfe2037173 n/a (libQt5Core.so.5)
                #3  0x00007fcfde711dd7 g_main_context_dispatch (libglib-2.0.so.0)
                #4  0x00007fcfde712040 n/a (libglib-2.0.so.0)
                #5  0x00007fcfde7120ec g_main_context_iteration (libglib-2.0.so.0)
                #6  0x00007fcfe203757f _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5)
                #7  0x00007fcfe1fe10da _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5)
                #8  0x00007fcfe1e040f3 _ZN7QThread4execEv (libQt5Core.so.5)
                #9  0x00007fcfe1e08d78 n/a (libQt5Core.so.5)
                #10 0x00007fcfe1208484 start_thread (libpthread.so.0)
                #11 0x00007fcfe15056dd __clone (libc.so.6)

                Stack trace of thread 8185:
                #0  0x00007fcfe1503cd1 get_nprocs (libc.so.6)
                #1  0x00007fcfe14d76c4 __sysconf (libc.so.6)
                #2  0x00007fcfe1e0809e _ZN7QThread16idealThreadCountEv (libQt5Core.so.5)
                #3  0x00007fcfe1e04c8d _ZN18QThreadPoolPrivateC1Ev (libQt5Core.so.5)
                #4  0x00007fcfe1e04d4f _ZN11QThreadPoolC1EP7QObject (libQt5Core.so.5)
                #5  0x00007fcfe1e04de6 _ZN11QThreadPool14globalInstanceEv (libQt5Core.so.5)
                #6  0x00007fcfe1fe46a3 _ZN16QCoreApplicationD2Ev (libQt5Core.so.5)
                #7  0x00007fcfe1fe4909 _ZN16QCoreApplicationD0Ev (libQt5Core.so.5)
                #8  0x000000000047bcba _ZN15ClipboardClientD1Ev (copyq)
                #9  0x000000000047857d main (copyq)
                #10 0x00007fcfe143e741 __libc_start_main (libc.so.6)
                #11 0x0000000000478869 _start (copyq)

[hluk]

I'm looking into this though I've seen the issue only once recently and it has been running flawlessly for more than two weeks now.

Last crash dump:

           PID: 11386 (copyq)
           UID: 1000 (lukas)
           GID: 100 (users)
        Signal: 11 (SEGV)
     Timestamp: Sat 2016-09-24 12:15:27 CEST (2 weeks 4 days ago)
  Command Line: /home/lukas/dev/build/copyq/debug/copyq eval --  if (monitoring()) {updateFirst()}
    Executable: /home/lukas/dev/build/copyq/debug/copyq
 Control Group: /
         Slice: -.slice
       Boot ID: 0d4235b2024345b8af5dc14b0d1f1aaa
    Machine ID: 8acd3484015edc90495d78bb4b7af4b1
      Hostname: laptop
       Message: Process 11386 (copyq) of user 1000 dumped core.

                Stack trace of thread 11387:
                #0  0x00007f642e53ec33 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5)
                #1  0x00007f642e5413fd _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt5Core.so.5)
                #2  0x00007f642e593173 n/a (libQt5Core.so.5)
                #3  0x00007f642ac97e67 g_main_context_dispatch (libglib-2.0.so.0)
                #4  0x00007f642ac980d0 n/a (libglib-2.0.so.0)
                #5  0x00007f642ac9817c g_main_context_iteration (libglib-2.0.so.0)
                #6  0x00007f642e59357f _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5)
                #7  0x00007f642e53d0da _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5)
                #8  0x00007f642e3600f3 _ZN7QThread4execEv (libQt5Core.so.5)
                #9  0x00007f642e364d78 n/a (libQt5Core.so.5)
                #10 0x00007f642d461454 start_thread (libpthread.so.0)
                #11 0x00007f642d75f7df __clone (libc.so.6)

                Stack trace of thread 11386:
                #0  0x00007f642e57205c _ZN7QObjectD1Ev (libQt5Core.so.5)
                #1  0x00007f642e540786 _ZN16QCoreApplicationD2Ev (libQt5Core.so.5)
                #2  0x00007f642e540909 _ZN16QCoreApplicationD0Ev (libQt5Core.so.5)
                #3  0x00000000004e2d1b _ZN21QScopedPointerDeleterI16QCoreApplicationE7cleanupEPS0_ (copyq)
                #4  0x00000000004e28cb _ZN14QScopedPointerI16QCoreApplication21QScopedPointerDeleterIS0_EED2Ev (copyq)
                #5  0x00000000004e1f33 _ZN3AppD2Ev (copyq)
                #6  0x00000000004e0d86 _ZN15ClipboardClientD2Ev (copyq)
                #7  0x00000000004ddea7 startClient (copyq)
                #8  0x00000000004de646 main (copyq)
                #9  0x00007f642d697291 __libc_start_main (libc.so.6)
                #10 0x00000000004db08a _start (copyq)

[hluk]

I managed to reproduce it with crazy bash command (crashed about twice in 1000 invocations of the client).

for x in $(seq 1000); do copyq eval 'copyq: if (monitoring()) {updateFirst()}' &; done

Anyway, it should be fixed now.