[Linux] Window manager logs warnings whenever TestCafe launches and/or closes browsers. Sometimes this leads to crashes.

Question

[Linux] Window manager logs warnings whenever TestCafe launches and/or closes browsers. Sometimes this leads to crashes.

titerman opened this issue 4 years ago · 3 comments

Overview

Warnings are logged whenever TestCafe launches and/or closes Chrome and Firefox. Sometimes, but not always, this leads to the window manager crashing, forcing the user to log out of the desktop environment.

Setup details

testcafe: 1.9.0-alpha.2
linux kernel: 5.7.9-1-MANJARO
X.Org (X11): 1.20.8
budgie-desktop: 10.5.1
firefox: 78.0.2
chromium: 84.0.4147.89

Test code:

import { Selector } from 'testcafe';

fixture `Devexpress`
    .page('https://www.devexpress.com');

test('Click the logo', async t => {
   await t.click('a#TOC-Logo');
});

Current behavior (Firefox):

journalctl output when the browser is opened:

Jul 23 16:11:25 eugene-manjaro budgie-wm.desktop[13188]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x8e00003
Jul 23 16:11:25 eugene-manjaro budgie-wm.desktop[13188]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x8e00003

and closed:

Jul 23 16:11:39 eugene-manjaro budgie-wm.desktop[13188]: Window manager warning: Receiving a NET_CLOSE_WINDOW message for 0x8e00003 without a timestamp!  This means some buggy (outdated) application is on the loose!
Jul 23 16:11:39 eugene-manjaro budgie-wm.desktop[13188]: Window manager warning: Tried to ping window 0x8e00003 with a bad serial! Not allowed.

Current behavior (Chromium):

Nothing when opened, the following when closed:

Jul 23 16:20:05 eugene-manjaro budgie-wm.desktop[13188]: Window manager warning: Receiving a NET_CLOSE_WINDOW message for 0x8c00001 without a timestamp!  This means some buggy (outdated) application is on the loose!
Jul 23 16:20:05 eugene-manjaro budgie-wm.desktop[13188]: Window manager warning: Tried to ping window 0x8c00001 with a bad serial! Not allowed.

Current behavior (WM crashing):

Triggered by the following test (cannot reliably replicate):

import { Selector, ClientFunction } from 'testcafe';

fixture `Devexpress`
    .page('https://www.devexpress.com');

test('Switch to the previous window', async t => {
    const testcafe = await t.openWindow('http://devexpress.github.io/testcafe')
          .switchToPreviousWindow();
});

journalctl:

Jul 23 14:43:49 eugene-manjaro budgie-wm[1686]: meta_window_is_focusable: assertion '!window->unmanaging' failed
Jul 23 14:43:49 eugene-manjaro budgie-wm[1686]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed
Jul 23 14:43:49 eugene-manjaro budgie-wm.desktop[1686]: Window manager warning: Receiving a NET_CLOSE_WINDOW message for 0x8800003 without a timestamp!  This means some buggy (outdated) application is on the loose!
Jul 23 14:43:49 eugene-manjaro budgie-wm.desktop[1686]: Window manager warning: Tried to ping window 0x8800003 with a bad serial! Not allowed.
Jul 23 14:43:49 eugene-manjaro budgie-wm[1686]: Could not create selection source for X11: Format TARGETS not supported
Jul 23 14:43:54 eugene-manjaro budgie-wm[1686]: g_object_new_valist: invalid unclassed object pointer for value type 'MetaWindow'
Jul 23 14:43:54 eugene-manjaro audit[1686]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=2 subj==unconfined pid=1686 comm="budgie-wm" exe="/usr/bin/budgie-wm" sig=11 res=1
Jul 23 14:43:54 eugene-manjaro kernel: budgie-wm[1686]: segfault at 78 ip 00007ffb0ee7355d sp 00007ffe4a5bdcb0 error 4 in libmutter-6.so.0.0.0[7ffb0edee000+14a000]
Jul 23 14:43:54 eugene-manjaro kernel: Code: 85 c0 0f 84 25 01 00 00 48 8b 35 8e b3 13 00 4c 89 e7 ff 15 1d 56 13 00 48 8b 68 18 48 89 c3 8b 40 20 85 c0 0f 89 93 01 00 00 <48> 8b 7d 78 48 85 ff 74 09 80 3f 00 0f 85 21 01 00 00 48 8d 35 ca
Jul 23 14:43:54 eugene-manjaro kernel: audit: type=1701 audit(1595504634.259:114): auid=1000 uid=1000 gid=1000 ses=2 subj==unconfined pid=1686 comm="budgie-wm" exe="/usr/bin/budgie-wm" sig=11 res=1
Jul 23 14:43:54 eugene-manjaro systemd[1]: Created slice system-systemd\x2dcoredump.slice.
Jul 23 14:43:54 eugene-manjaro audit: BPF prog-id=21 op=LOAD
Jul 23 14:43:54 eugene-manjaro kernel: audit: type=1334 audit(1595504634.279:115): prog-id=21 op=LOAD
Jul 23 14:43:54 eugene-manjaro kernel: audit: type=1334 audit(1595504634.279:116): prog-id=22 op=LOAD
Jul 23 14:43:54 eugene-manjaro audit: BPF prog-id=22 op=LOAD
Jul 23 14:43:54 eugene-manjaro audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=systemd-coredump@0-12790-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=succes>
Jul 23 14:43:54 eugene-manjaro systemd[1]: Started Process Core Dump (PID 12790/UID 0).
Jul 23 14:43:54 eugene-manjaro kernel: audit: type=1130 audit(1595504634.282:117): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=systemd-coredump@0-12790-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? >
Jul 23 14:43:55 eugene-manjaro gnome-session[1480]: gnome-session-binary[1480]: WARNING: Application 'budgie-wm.desktop' killed by signal 11
Jul 23 14:43:55 eugene-manjaro gnome-session-binary[1480]: WARNING: Application 'budgie-wm.desktop' killed by signal 11

Expected behaviour:

No warnings, no crashes.

Answer 1 · 2020-07-27T07:48:44.000Z

We need to provide timestamps for the X protocol messages.

Answer 2 · 2022-12-10T01:57:34.000Z

This issue has been automatically marked as stale because it has not had any activity for a long period. It will be closed and archived if no further activity occurs. However, we may return to this issue in the future. If it still affects you or you have any additional information regarding it, please leave a comment and we will keep it open.

Answer 3 · 2022-12-21T01:54:45.000Z

We're closing this issue after a prolonged period of inactivity. If it still affects you, please add a comment to this issue with up-to-date information. Thank you.