Gnome-shell-extension-gsconnect: Stack trace for context 0x55e741ae21a0

[makuser]

Describe the bug
Some sort of garbage collector bug, I assume. CPU usage of one of the gjs threads was around 60-80% until I killed the thread, and then the syslog spam immediately stopped. Unfortunately I did not remember exactly at which time I killed the thread.

How I noticed the issue:

-rw-r----- 1 syslog adm 82G Jul  8 21:20 /var/log/syslog

Additionally an unusually high CPU cooling was required, which turned out to be gjs.

Steps To Reproduce:
Unfortunately I have no idea yet.

Expected behavior
Not crash and spam my syslog for hours until just 0K are left on disk.

Support Log

Jul  8 17:24:21 MAKpc gjs[301420]: JS WARNING: [/home/marc/.local/share/gnome-shell/extensions/[email protected]/preferences/device.js 946]: reference to undefined property "photo"
Jul  8 17:24:49 MAKpc gnome-shell[4388]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0001f
Jul  8 17:24:59 MAKpc /usr/lib/gdm3/gdm-x-session[4159]: (EE) client bug: timer event4 debounce: scheduled expiry is in the past (-13ms), your system is too slow
Jul  8 17:24:59 MAKpc /usr/lib/gdm3/gdm-x-session[4159]: (EE) client bug: timer event4 debounce short: scheduled expiry is in the past (-26ms), your system is too slow
Jul  8 17:25:39 MAKpc gjs[4667]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Jul  8 17:25:39 MAKpc org.gnome.Shell.Extensions.GSConnect[4667]: == Stack trace for context 0x55e741ae21a0 ==
Jul  8 17:25:39 MAKpc org.gnome.Shell.Extensions.GSConnect[4667]: #0   7ffd84d35900 I   /home/marc/.local/share/gnome-shell/extensions/[email protected]/service/plugins/sms.js:286 (281ad6783d30 @ 488)
Jul  8 17:25:39 MAKpc org.gnome.Shell.Extensions.GSConnect[4667]: #1   7ffd84d35970 I   /home/marc/.local/share/gnome-shell/extensions/[email protected]/service/plugins/sms.js:328 (281ad6783e98 @ 451)
Jul  8 17:25:39 MAKpc org.gnome.Shell.Extensions.GSConnect[4667]: #2   7ffd84d35a30 b   /home/marc/.local/share/gnome-shell/extensions/[email protected]/service/plugins/sms.js:175 (281ad67839e8 @ 54)
Jul  8 17:25:39 MAKpc org.gnome.Shell.Extensions.GSConnect[4667]: #3   7ffd84d35b00 b   /home/marc/.local/share/gnome-shell/extensions/[email protected]/service/device.js:441 (6fe19ce59e8 @ 194)
Jul  8 17:25:39 MAKpc org.gnome.Shell.Extensions.GSConnect[4667]: #4   7ffd84d35bd0 b   /home/marc/.local/share/gnome-shell/extensions/[email protected]/service/protocol/core.js:299 (6fe19cdd268 @ 199)
Jul  8 17:25:39 MAKpc org.gnome.Shell.Extensions.GSConnect[4667]: #5   55e741b92810 i   /home/marc/.local/share/gnome-shell/extensions/[email protected]/service/daemon.js:1132 (6fe19c8d178 @ 1324)
Jul  8 17:25:39 MAKpc gjs[4667]: The offending signal was notify on GSConnectSMSPlugin 0x55e7424f4320.
Jul  8 17:25:39 MAKpc gjs[4667]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked.
Jul  8 17:25:39 MAKpc org.gnome.Shell.Extensions.GSConnect[4667]: == Stack trace for context 0x55e741ae21a0 ==
Jul  8 17:25:39 MAKpc org.gnome.Shell.Extensions.GSConnect[4667]: #0   55e741b92810 i   /home/marc/.local/share/gnome-shell/extensions/[email protected]/service/daemon.js:1132 (6fe19c8d178 @ 1324)
Jul  8 17:25:39 MAKpc gjs[4667]: The offending callback was AsyncReadyCallback().
Jul  8 17:25:39 MAKpc gjs[4667]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked.
Jul  8 17:25:39 MAKpc org.gnome.Shell.Extensions.GSConnect[4667]: == Stack trace for context 0x55e741ae21a0 ==
Jul  8 17:25:39 MAKpc org.gnome.Shell.Extensions.GSConnect[4667]: #0   55e741b92810 i   /home/marc/.local/share/gnome-shell/extensions/[email protected]/service/daemon.js:1132 (6fe19c8d178 @ 1324)
Jul  8 17:25:39 MAKpc gjs[4667]: The offending callback was AsyncReadyCallback().
Jul  8 17:25:41 MAKpc gjs[4667]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked.
Jul  8 17:25:41 MAKpc org.gnome.Shell.Extensions.GSConnect[4667]: == Stack trace for context 0x55e741ae21a0 ==
Jul  8 17:25:41 MAKpc org.gnome.Shell.Extensions.GSConnect[4667]: #0   55e741b92810 i   /home/marc/.local/share/gnome-shell/extensions/[email protected]/service/daemon.js:1132 (6fe19c8d178 @ 1324)
Jul  8 17:25:41 MAKpc gjs[4667]: The offending callback was SourceFunc().
Jul  8 17:25:41 MAKpc gjs[4667]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked.
Jul  8 17:25:41 MAKpc org.gnome.Shell.Extensions.GSConnect[4667]: == Stack trace for context 0x55e741ae21a0 ==
Jul  8 17:25:41 MAKpc org.gnome.Shell.Extensions.GSConnect[4667]: #0   55e741b92810 i   /home/marc/.local/share/gnome-shell/extensions/[email protected]/service/daemon.js:1132 (6fe19c8d178 @ 1324)
Jul  8 17:25:41 MAKpc org.gnome.Shell.Extensions.GSConnect[4667]: == Stack trace for context 0x55e741ae21a0 ==
Jul  8 17:25:41 MAKpc org.gnome.Shell.Extensions.GSConnect[4667]: #0   55e741b92810 i   /home/marc/.local/share/gnome-shell/extensions/[email protected]/service/daemon.js:1132 (6fe19c8d178 @ 1324)
Jul  8 17:25:41 MAKpc org.gnome.Shell.Extensions.GSConnect[4667]: == Stack trace for context 0x55e741ae21a0 ==
Jul  8 17:25:41 MAKpc org.gnome.Shell.Extensions.GSConnect[4667]: #0   55e741b92810 i   /home/marc/.local/share/gnome-shell/extensions/[email protected]/service/daemon.js:1132 (6fe19c8d178 @ 1324)
Jul  8 17:25:41 MAKpc org.gnome.Shell.Extensions.GSConnect[4667]: == Stack trace for context 0x55e741ae21a0 ==
Jul  8 17:25:41 MAKpc gjs[4667]: The offending callback was SourceFunc().
Jul  8 17:25:41 MAKpc org.gnome.Shell.Extensions.GSConnect[4667]: #0   55e741b92810 i   /home/marc/.local/share/gnome-shell/extensions/[email protected]/service/daemon.js:1132 (6fe19c8d178 @ 1324)
Jul  8 17:25:41 MAKpc org.gnome.Shell.Extensions.GSConnect[4667]: == Stack trace for context 0x55e741ae21a0 ==
Jul  8 17:25:41 MAKpc org.gnome.Shell.Extensions.GSConnect[4667]: #0   55e741b92810 i   /home/marc/.local/share/gnome-shell/extensions/[email protected]/service/daemon.js:1132 (6fe19c8d178 @ 1324)
Jul  8 17:25:41 MAKpc org.gnome.Shell.Extensions.GSConnect[4667]: == Stack trace for context 0x55e741ae21a0 ==
Jul  8 17:25:41 MAKpc org.gnome.Shell.Extensions.GSConnect[4667]: #0   55e741b92810 i   /home/marc/.local/share/gnome-shell/extensions/[email protected]/service/daemon.js:1132 (6fe19c8d178 @ 1324)
Jul  8 17:25:41 MAKpc org.gnome.Shell.Extensions.GSConnect[4667]: == Stack trace for context 0x55e741ae21a0 ==
Jul  8 17:25:41 MAKpc org.gnome.Shell.Extensions.GSConnect[4667]: #0   55e741b92810 i   /home/marc/.local/share/gnome-shell/extensions/[email protected]/service/daemon.js:1132 (6fe19c8d178 @ 1324)
Jul  8 17:25:41 MAKpc org.gnome.Shell.Extensions.GSConnect[4667]: == Stack trace for context 0x55e741ae21a0 ==
Jul  8 17:25:41 MAKpc org.gnome.Shell.Extensions.GSConnect[4667]: #0   55e741b92810 i   /home/marc/.local/share/gnome-shell/extensions/[email protected]/service/daemon.js:1132 (6fe19c8d178 @ 1324)
[...]
Jul  8 17:25:41 MAKpc gjs[4667]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked.
Jul  8 17:25:41 MAKpc gjs[4667]: The offending callback was SourceFunc().
Jul  8 17:25:41 MAKpc gjs[4667]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked.
Jul  8 17:25:41 MAKpc gjs[4667]: The offending callback was SourceFunc().
Jul  8 17:25:41 MAKpc gjs[4667]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked.
Jul  8 17:25:41 MAKpc gjs[4667]: The offending callback was SourceFunc().
Jul  8 17:25:41 MAKpc gjs[4667]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked.
Jul  8 17:25:41 MAKpc gjs[4667]: The offending callback was SourceFunc().
Jul  8 17:25:41 MAKpc gjs[4667]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked.
Jul  8 17:25:41 MAKpc gjs[4667]: The offending callback was SourceFunc().
Jul  8 17:25:41 MAKpc gjs[4667]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked.
Jul  8 17:25:41 MAKpc gjs[4667]: The offending callback was SourceFunc().
[...]
Jul  8 21:04:32 MAKpc org.gnome.Shell.Extensions.GSConnect[4667]: == Stack trace for context 0x55e741ae21a0 ==
Jul  8 21:04:32 MAKpc org.gnome.Shell.Extensions.GSConnect[4667]: #0   55e741b92810 i   /home/marc/.local/share/gnome-shell/extensions/[email protected]/service/daemon.js:1132 (6fe19c8d178 @ 1324)
Jul  8 21:04:32 MAKpc gjs[4667]: The offending callback was SourceFunc().
Jul  8 21:04:32 MAKpc gjs[4667]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked.
[...]
Jul  8 21:05:08 MAKpc gjs[4667]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked.
Jul  8 21:05:08 MAKpc gjs[4667]: The offending callback was SourceFunc().
Jul  8 21:05:08 MAKpc dbus-daemon[4029]: [session uid=1000 pid=4029] Monitoring connection :1.86 closed.
Jul  8 21:05:08 MAKpc gnome-shell[4388]: JS ERROR: TypeError: malformed UTF-8 character sequence at offset 0
Jul  8 21:05:08 MAKpc dbus-daemon[4029]: [session uid=1000 pid=4029] Activating service name='org.gnome.Shell.Extensions.GSConnect' requested by ':1.54' (uid=1000 pid=4388 comm="/usr/bin/gnome-shell " label="unconfined")
Jul  8 21:05:08 MAKpc dbus-daemon[4029]: [session uid=1000 pid=4029] Successfully activated service 'org.gnome.Shell.Extensions.GSConnect'
Jul  8 21:05:08 MAKpc gjs[360637]: g_variant_new_string: assertion 'string != NULL' failed
Jul  8 21:05:08 MAKpc dbus-daemon[4029]: [session uid=1000 pid=4029] Connection :1.392 (uid=1000 pid=360637 comm="gjs /home/marc/.local/share/gnome-shell/extensions" label="unconfined") became a monitor.
Jul  8 21:05:08 MAKpc gjs[360637]: gvc_mixer_card_get_index: assertion 'GVC_IS_MIXER_CARD (card)' failed
Jul  8 21:05:08 MAKpc gjs[360637]: message repeated 2 times: [ gvc_mixer_card_get_index: assertion 'GVC_IS_MIXER_CARD (card)' failed]
Jul  8 21:05:46 MAKpc systemd[4000]: Started Application launched by gnome-shell.
Jul  8 21:05:48 MAKpc dbus-daemon[4029]: [session uid=1000 pid=4029] Activating service name='org.gnome.ChromeGnomeShell' requested by ':1.405' (uid=1000 pid=361203 comm="/usr/bin/python3 /usr/bin/chrome-gnome-shell /usr/" label="unconfined")
Jul  8 21:05:48 MAKpc dbus-daemon[4029]: [session uid=1000 pid=4029] Successfully activated service 'org.gnome.ChromeGnomeShell'
Jul  8 21:06:46 MAKpc gnome-shell[360822]: ###!!! [Parent][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost
Jul  8 21:06:46 MAKpc gnome-shell[360822]: message repeated 7 times: [ ###!!! [Parent][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost]
Jul  8 21:07:03 MAKpc /usr/lib/gdm3/gdm-x-session[4159]: (EE) client bug: timer event4 debounce short: scheduled expiry is in the past (-3ms), your system is too slow
Jul  8 21:07:21 MAKpc gnome-shell[360822]: ###!!! [Parent][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost
Jul  8 21:07:21 MAKpc gnome-shell[360822]: message repeated 3 times: [ ###!!! [Parent][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost]
Jul  8 21:07:42 MAKpc systemd[4000]: Started VTE child process 362030 launched by gnome-terminal-server process 290593.
Jul  8 21:12:21 MAKpc dbus-daemon[4029]: [session uid=1000 pid=4029] Activating service name='org.gnome.ChromeGnomeShell' requested by ':1.411' (uid=1000 pid=363404 comm="/usr/bin/python3 /usr/bin/chrome-gnome-shell /usr/" label="unconfined")
Jul  8 21:12:21 MAKpc dbus-daemon[4029]: [session uid=1000 pid=4029] Successfully activated service 'org.gnome.ChromeGnomeShell'

System Details (please complete the following information):

• GSConnect version: 39
  
  
  
  • Installed from: https://extensions.gnome.org/extension/1319/gsconnect/
  
  
• GNOME/Shell version: 3.36.3-1ubuntu1~20.04.2
• Distro/Release: Ubuntu 20.04 LTS / 5.4.0-40-generic #44-Ubuntu

GSConnect environment (if applicable):

• Paired Device(s): OnePlus 5
• KDE Connect app version: 1.14.2 via Play Store
• Plugin(s):
  Mobile App: all available modules except "Receive Notifications, Bigscreen remote" (Filesystem-Sharing, Media Control, Publish and receive, Battery report, Notification sync, Start Camera, Phone-Integration, Find remote Device, Clipboard sync, send SMS, Ping, Find my phone, Change system volume, Remote Control for Presentations, Receiver for Keyboard input, Media Control, Contact sync, Execute command, Remote input)
  Desktop: all available modules (Battery, Clipboard, Contacts, Find my phone, Mousepad, MPRIS, Notifications, Photos, Ping, Presentations, Execute command, SFTP, Share, SMS, System volume, Phone)
  _My locale is de_DE.UTF-8, so I translated the plugin names into en._

Additional Notes:
I only paired my phone to GSConnect a few hours before, could have been around 17:24 that I see in the logs and unpaired KDE-Connect after that. KDE-Connect is still running in the bg+notification area, but not paired to the phone. GSConnect had been installed for the last few days already though, without this bug.

Locale is de_DE.UTF-8 on my machine, and my phone is set to German too, in case it might be connected to Jul 8 21:05:08 MAKpc gnome-shell[4388]: JS ERROR: TypeError: malformed UTF-8 character sequence at offset 0

I have several audio devices, in case it might have anything to do with Jul 8 21:05:08 MAKpc gjs[360637]: gvc_mixer_card_get_index: assertion 'GVC_IS_MIXER_CARD (card)' failed and I switch between them on a regular basis, primarily the output profiles. Not at this time of the log entry though.

Card #0
    Name: alsa_card.usb-Blue_Microphones_Yeti_Stereo_Microphone_REV8-00
    Driver: module-alsa-card.c
    Owner Module: 22
    Properties:
        alsa.card = "1"
        alsa.card_name = "Yeti Stereo Microphone"
        alsa.long_card_name = "Blue Microphones Yeti Stereo Microphone at usb-0000:00:14.0-13, full speed"
        alsa.driver_name = "snd_usb_audio"
        device.bus_path = "pci-0000:00:14.0-usb-0:13:1.0"
        sysfs.path = "/devices/pci0000:00/0000:00:14.0/usb1/1-13/1-13:1.0/sound/card1"
        udev.id = "usb-Blue_Microphones_Yeti_Stereo_Microphone_REV8-00"
        device.bus = "usb"
        device.vendor.id = "b58e"
        device.vendor.name = "Blue Microphones"
        device.product.id = "9e84"
        device.product.name = "Yeti Stereo Microphone"
        device.serial = "Blue_Microphones_Yeti_Stereo_Microphone_REV8"
        device.form_factor = "microphone"
        device.string = "1"
        device.description = "Yeti Stereo Microphone"
        module-udev-detect.discovered = "1"
        device.icon_name = "audio-input-microphone-usb"
    Profiles:
        input:analog-stereo: Analog Stereo-Eingabe (sinks: 0, sources: 1, priority: 65, available: yes)
        input:iec958-stereo: Digital Stereo (IEC958)-Eingabe (sinks: 0, sources: 1, priority: 55, available: yes)
        output:analog-stereo: Analog Stereo-Ausgabe (sinks: 1, sources: 0, priority: 6500, available: yes)
        output:analog-stereo+input:analog-stereo: Analog Stereo Duplex (sinks: 1, sources: 1, priority: 6565, available: yes)
        output:analog-stereo+input:iec958-stereo: Analog Stereo-Ausgabe + Digital Stereo (IEC958)-Eingabe (sinks: 1, sources: 1, priority: 6555, available: yes)
        output:iec958-stereo: Digital Stereo (IEC958)-Ausgabe (sinks: 1, sources: 0, priority: 5500, available: yes)
        output:iec958-stereo+input:analog-stereo: Digital Stereo (IEC958)-Ausgabe + Analog Stereo-Eingabe (sinks: 1, sources: 1, priority: 5565, available: yes)
        output:iec958-stereo+input:iec958-stereo: Digital Stereo Duplex (IEC958) (sinks: 1, sources: 1, priority: 5555, available: yes)
        output:iec958-ac3-surround-51: Digital Surround 5.1 (IEC958/AC3)-Ausgabe (sinks: 1, sources: 0, priority: 300, available: yes)
        output:iec958-ac3-surround-51+input:analog-stereo: Digital Surround 5.1 (IEC958/AC3)-Ausgabe + Analog Stereo-Eingabe (sinks: 1, sources: 1, priority: 365, available: yes)
        output:iec958-ac3-surround-51+input:iec958-stereo: Digital Surround 5.1 (IEC958/AC3)-Ausgabe + Digital Stereo (IEC958)-Eingabe (sinks: 1, sources: 1, priority: 355, available: yes)
        off: Aus (sinks: 0, sources: 0, priority: 0, available: yes)
    Active Profile: input:iec958-stereo
    Ports:
        analog-input-mic: Mikrofon (priority: 8700, latency offset: 0 usec)
            Properties:
                device.icon_name = "audio-input-microphone"
            Part of profile(s): input:analog-stereo, output:analog-stereo+input:analog-stereo, output:iec958-stereo+input:analog-stereo, output:iec958-ac3-surround-51+input:analog-stereo
        iec958-stereo-input: Digitaleingang (S/PDIF) (priority: 0, latency offset: 0 usec)
            Part of profile(s): input:iec958-stereo, output:analog-stereo+input:iec958-stereo, output:iec958-stereo+input:iec958-stereo, output:iec958-ac3-surround-51+input:iec958-stereo
        analog-output-speaker: Lautsprecher (priority: 10000, latency offset: 0 usec)
            Properties:
                device.icon_name = "audio-speakers"
            Part of profile(s): output:analog-stereo, output:analog-stereo+input:analog-stereo, output:analog-stereo+input:iec958-stereo
        iec958-stereo-output: Digitalausgang (S/PDIF) (priority: 0, latency offset: 0 usec)
            Part of profile(s): output:iec958-stereo, output:iec958-stereo+input:analog-stereo, output:iec958-stereo+input:iec958-stereo

Card #1
    Name: alsa_card.pci-0000_01_00.1
    Driver: module-alsa-card.c
    Owner Module: 23
    Properties:
        alsa.card = "3"
        alsa.card_name = "HDA NVidia"
        alsa.long_card_name = "HDA NVidia at 0xed080000 irq 17"
        alsa.driver_name = "snd_hda_intel"
        device.bus_path = "pci-0000:01:00.1"
        sysfs.path = "/devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card3"
        device.bus = "pci"
        device.vendor.id = "10de"
        device.vendor.name = "NVIDIA Corporation"
        device.product.id = "10f0"
        device.product.name = "GP104 High Definition Audio Controller"
        device.string = "3"
        device.description = "GP104 High Definition Audio Controller"
        module-udev-detect.discovered = "1"
        device.icon_name = "audio-card-pci"
    Profiles:
        output:hdmi-stereo: Digital Stereo (HDMI)-Ausgabe (sinks: 1, sources: 0, priority: 5900, available: yes)
        output:hdmi-surround: Digital Surround 5.1 (HDMI)-Ausgabe (sinks: 1, sources: 0, priority: 800, available: yes)
        output:hdmi-stereo-extra1: Digital Stereo (HDMI 2)-Ausgabe (sinks: 1, sources: 0, priority: 5700, available: yes)
        output:hdmi-stereo-extra2: Digital Stereo (HDMI 3)-Ausgabe (sinks: 1, sources: 0, priority: 5700, available: no)
        output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI 3)-Ausgabe (sinks: 1, sources: 0, priority: 600, available: no)
        output:hdmi-surround71-extra2: Digital Surround 7.1 (HDMI 3)-Ausgabe (sinks: 1, sources: 0, priority: 600, available: no)
        output:hdmi-stereo-extra3: Digital Stereo (HDMI 4)-Ausgabe (sinks: 1, sources: 0, priority: 5700, available: no)
        output:hdmi-surround-extra3: Digital Surround 5.1 (HDMI 4)-Ausgabe (sinks: 1, sources: 0, priority: 600, available: no)
        output:hdmi-surround71-extra3: Digital Surround 7.1 (HDMI 4)-Ausgabe (sinks: 1, sources: 0, priority: 600, available: no)
        off: Aus (sinks: 0, sources: 0, priority: 0, available: yes)
    Active Profile: off
    Ports:
        hdmi-output-0: HDMI / DisplayPort (priority: 5900, latency offset: 0 usec, available)
            Properties:
                device.icon_name = "video-display"
                device.product.name = "34UM95
      "
            Part of profile(s): output:hdmi-stereo, output:hdmi-surround
        hdmi-output-1: HDMI / DisplayPort 2 (priority: 5800, latency offset: 0 usec, available)
            Properties:
                device.icon_name = "video-display"
            Part of profile(s): output:hdmi-stereo-extra1
        hdmi-output-2: HDMI / DisplayPort 3 (priority: 5700, latency offset: 0 usec, not available)
            Properties:
                device.icon_name = "video-display"
            Part of profile(s): output:hdmi-stereo-extra2, output:hdmi-surround-extra2, output:hdmi-surround71-extra2
        hdmi-output-3: HDMI / DisplayPort 4 (priority: 5600, latency offset: 0 usec, not available)
            Properties:
                device.icon_name = "video-display"
            Part of profile(s): output:hdmi-stereo-extra3, output:hdmi-surround-extra3, output:hdmi-surround71-extra3

Card #3
    Name: alsa_card.pci-0000_00_1f.3
    Driver: module-alsa-card.c
    Owner Module: 25
    Properties:
        alsa.card = "2"
        alsa.card_name = "HDA Intel PCH"
        alsa.long_card_name = "HDA Intel PCH at 0xed440000 irq 158"
        alsa.driver_name = "snd_hda_intel"
        device.bus_path = "pci-0000:00:1f.3"
        sysfs.path = "/devices/pci0000:00/0000:00:1f.3/sound/card2"
        device.bus = "pci"
        device.vendor.id = "8086"
        device.vendor.name = "Intel Corporation"
        device.product.id = "a170"
        device.product.name = "100 Series/C230 Series Chipset Family HD Audio Controller"
        device.form_factor = "internal"
        device.string = "2"
        device.description = "Eingebautes Tongerät"
        module-udev-detect.discovered = "1"
        device.icon_name = "audio-card-pci"
    Profiles:
        input:analog-stereo: Analog Stereo-Eingabe (sinks: 0, sources: 1, priority: 65, available: yes)
        output:analog-stereo: Analog Stereo-Ausgabe (sinks: 1, sources: 0, priority: 6500, available: yes)
        output:analog-stereo+input:analog-stereo: Analog Stereo Duplex (sinks: 1, sources: 1, priority: 6565, available: yes)
        output:analog-surround-21: Analog Surround 2.1-Ausgabe (sinks: 1, sources: 0, priority: 1300, available: no)
        output:analog-surround-21+input:analog-stereo: Analog Surround 2.1-Ausgabe + Analog Stereo-Eingabe (sinks: 1, sources: 1, priority: 1365, available: no)
        output:analog-surround-40: Analog Surround 4.0-Ausgabe (sinks: 1, sources: 0, priority: 1200, available: no)
        output:analog-surround-40+input:analog-stereo: Analog Surround 4.0-Ausgabe + Analog Stereo-Eingabe (sinks: 1, sources: 1, priority: 1265, available: no)
        output:analog-surround-41: Analog Surround 4.1-Ausgabe (sinks: 1, sources: 0, priority: 1300, available: no)
        output:analog-surround-41+input:analog-stereo: Analog Surround 4.1-Ausgabe + Analog Stereo-Eingabe (sinks: 1, sources: 1, priority: 1365, available: no)
        output:analog-surround-50: Analog Surround 5.0-Ausgabe (sinks: 1, sources: 0, priority: 1200, available: no)
        output:analog-surround-50+input:analog-stereo: Analog Surround 5.0-Ausgabe + Analog Stereo-Eingabe (sinks: 1, sources: 1, priority: 1265, available: no)
        output:analog-surround-51: Analog Surround 5.1-Ausgabe (sinks: 1, sources: 0, priority: 1300, available: no)
        output:analog-surround-51+input:analog-stereo: Analog Surround 5.1-Ausgabe + Analog Stereo-Eingabe (sinks: 1, sources: 1, priority: 1365, available: no)
        output:iec958-stereo: Digital Stereo (IEC958)-Ausgabe (sinks: 1, sources: 0, priority: 5500, available: yes)
        output:iec958-stereo+input:analog-stereo: Digital Stereo (IEC958)-Ausgabe + Analog Stereo-Eingabe (sinks: 1, sources: 1, priority: 5565, available: yes)
        output:iec958-ac3-surround-51: Digital Surround 5.1 (IEC958/AC3)-Ausgabe (sinks: 1, sources: 0, priority: 300, available: yes)
        output:iec958-ac3-surround-51+input:analog-stereo: Digital Surround 5.1 (IEC958/AC3)-Ausgabe + Analog Stereo-Eingabe (sinks: 1, sources: 1, priority: 365, available: yes)
        off: Aus (sinks: 0, sources: 0, priority: 0, available: yes)
    Active Profile: output:analog-stereo
    Ports:
        analog-input-front-mic: Vorderes Mikrofon (priority: 8500, latency offset: 0 usec, available)
            Properties:
                device.icon_name = "audio-input-microphone"
            Part of profile(s): input:analog-stereo, output:analog-stereo+input:analog-stereo, output:analog-surround-21+input:analog-stereo, output:analog-surround-40+input:analog-stereo, output:analog-surround-41+input:analog-stereo, output:analog-surround-50+input:analog-stereo, output:analog-surround-51+input:analog-stereo, output:iec958-stereo+input:analog-stereo, output:iec958-ac3-surround-51+input:analog-stereo
        analog-input-rear-mic: Rückwärtiges Mikrofon (priority: 8200, latency offset: 0 usec, not available)
            Properties:
                device.icon_name = "audio-input-microphone"
            Part of profile(s): input:analog-stereo, output:analog-stereo+input:analog-stereo, output:analog-surround-21+input:analog-stereo, output:analog-surround-40+input:analog-stereo, output:analog-surround-41+input:analog-stereo, output:analog-surround-50+input:analog-stereo, output:analog-surround-51+input:analog-stereo, output:iec958-stereo+input:analog-stereo, output:iec958-ac3-surround-51+input:analog-stereo
        analog-input-linein: Eingang (priority: 8100, latency offset: 0 usec, not available)
            Part of profile(s): input:analog-stereo, output:analog-stereo+input:analog-stereo, output:analog-surround-21+input:analog-stereo, output:analog-surround-40+input:analog-stereo, output:analog-surround-41+input:analog-stereo, output:analog-surround-50+input:analog-stereo, output:analog-surround-51+input:analog-stereo, output:iec958-stereo+input:analog-stereo, output:iec958-ac3-surround-51+input:analog-stereo
        analog-output-lineout: Line-Ausgang (priority: 9000, latency offset: 0 usec, not available)
            Part of profile(s): output:analog-stereo, output:analog-stereo+input:analog-stereo, output:analog-surround-21, output:analog-surround-21+input:analog-stereo, output:analog-surround-40, output:analog-surround-40+input:analog-stereo, output:analog-surround-41, output:analog-surround-41+input:analog-stereo, output:analog-surround-50, output:analog-surround-50+input:analog-stereo, output:analog-surround-51, output:analog-surround-51+input:analog-stereo
        analog-output-headphones: Kopfhörer (priority: 9900, latency offset: 0 usec, available)
            Properties:
                device.icon_name = "audio-headphones"
            Part of profile(s): output:analog-stereo, output:analog-stereo+input:analog-stereo
        iec958-stereo-output: Digitalausgang (S/PDIF) (priority: 0, latency offset: 0 usec)
            Part of profile(s): output:iec958-stereo, output:iec958-stereo+input:analog-stereo

Card #5
    Name: alsa_card.usb-046d_0825_4177FDE0-02
    Driver: module-alsa-card.c
    Owner Module: 32
    Properties:
        alsa.card = "0"
        alsa.card_name = "USB Device 0x46d:0x825"
        alsa.long_card_name = "USB Device 0x46d:0x825 at usb-0000:00:14.0-6.3.1, high speed"
        alsa.driver_name = "snd_usb_audio"
        device.bus_path = "pci-0000:00:14.0-usb-0:6.3.1:1.2"
        sysfs.path = "/devices/pci0000:00/0000:00:14.0/usb1/1-6/1-6.3/1-6.3.1/1-6.3.1:1.2/sound/card0"
        udev.id = "usb-046d_0825_4177FDE0-02"
        device.bus = "usb"
        device.vendor.id = "046d"
        device.vendor.name = "Logitech, Inc."
        device.product.id = "0825"
        device.product.name = "Webcam C270"
        device.serial = "046d_0825_4177FDE0"
        device.form_factor = "webcam"
        device.string = "0"
        device.description = "Webcam C270"
        module-udev-detect.discovered = "1"
        device.icon_name = "camera-web-usb"
    Profiles:
        input:mono-fallback: Mono-Eingabe (sinks: 0, sources: 1, priority: 1, available: yes)
        input:multichannel-input: Mehrkanal-Eingabe (sinks: 0, sources: 1, priority: 1, available: yes)
        off: Aus (sinks: 0, sources: 0, priority: 0, available: yes)
    Active Profile: off
    Ports:
        analog-input-mic: Mikrofon (priority: 8700, latency offset: 0 usec)
            Properties:
                device.icon_name = "audio-input-microphone"
            Part of profile(s): input:mono-fallback
        multichannel-input: Mehrkanaleingang (priority: 0, latency offset: 0 usec)
            Part of profile(s): input:multichannel-input

[ferdnyc]

The pulseaudio messages, in particular, _might_ be unrelated. They're coming from a different gjs process than the rest of the GSConnect messages. (gjs[360637], as opposed to gjs[4667] which is GSConnect's daemon.js.)

[andyholmes]

The pulseaudio messages, in particular, might be unrelated.

I think you're right about that. I'm at least sure that there is no GSourceFunc/GAsyncReadyCallback related code that could cause this in that component.

Jul 8 17:25:39 MAKpc gjs[4667]: The offending callback was AsyncReadyCallback().

Thanks for reporting for thorough logs. We've had a number of similar bugs to this (that I can't reproduce), but this is the first indicating what might have started the whole problem.

For context, we can run some functions in threads via GTask, which work by running code in a dedicated thread, then returning to the original thread to invoke the GAsyncReadyCallback (this is what makes it safe to do in JavaScript). I suspect that GLib uses a GSourceFunc to ensure the callback is invoked in the correct thread and when that fails, the GSourceFunc keeps getting called and fails.

Could you tell me, did you have the Messaging window open at some point during your usage of GSConnect?

[andyholmes]

Minor update: one way or the other there's a bug in GSConnect since we're hitting a potential segfault and I have a good place to start looking now

Ultimately, I think it might be GJS's segfault-guard that's causing the log spam and I've chatted briefly with the maintainer who thinks I may be right.

cc #800

[makuser]

The pulseaudio messages, in particular, _might_ be unrelated. They're coming from a different gjs process than the rest of the GSConnect messages. (gjs[360637], as opposed to gjs[4667] which is GSConnect's daemon.js.)

Oh, right... Totally overlooked that.

Thanks for reporting for thorough logs. We've had a number of similar bugs to this (that I can't reproduce), but this is the first indicating what might have started the whole problem.

Sure thing!

Could you tell me, did you have the Messaging window open at some point during your usage of GSConnect?

Yes. So after installing the extension several days ago, I paired the mobile only yesterday, then left it for a few minutes and then I did this:

• I started "find my phone", but my phone did not ring at that time
• I then tried the remote keyboard, but it said "Remote keyboard on MAKoneplus 5 is not active".
• I went to my phone and checked the app to see if the remote keyboard extension is enabled or not, which it is, so I don't know why GSConnect said its not active.
• I then noticed the phone is also connected with KDE Connect on my desktop, showed fingerprints in both GSConnect and KDE Connect and compared it to the profiles on the phone. The keyboard ext was also enabled in the GSConnect profile.
• Tried the Messages function in GSConnect, but the list was empty at the time
• Do some other stuff for about two minutes.
• Phone rang due to find my phone from GSConnect, I hit "I found it" and it stopped.
• I unpaired the phone in KDE Connect from the desktop, phone dropped the connection to KDE Connect immediately and was only connected to GSConnect from then on.
• Went on with my work
• Left PC for dinner
• came back and the drive was full due to logs

I just repeated all that, without the pairing though because it's already paired and also without the waiting, but I was not able to reproduce it this way. The Messages app also shows messages now, which it did not before.

But when switching to a thread that I have not opened before, I get this:

Jul 09 13:16:07 MAKpc gjs[360637]: JS ERROR: TypeError: row1.message is undefined
                                   _sortMessages@/home/marc/.local/share/gnome-shell/extensions/[email protected]/service/ui/messaging.js:712:9
                                   logPrevious@/home/marc/.local/share/gnome-shell/extensions/[email protected]/service/ui/messaging.js:759:23
                                   _populateMessages@/home/marc/.local/share/gnome-shell/extensions/[email protected]/service/ui/messaging.js:632:18
                                   _init@/home/marc/.local/share/gnome-shell/extensions/[email protected]/service/ui/messaging.js:392:14
                                   set thread_id@/home/marc/.local/share/gnome-shell/extensions/[email protected]/service/ui/messaging.js:897:28
                                   _onThreadSelected@/home/marc/.local/share/gnome-shell/extensions/[email protected]/service/ui/messaging.js:1037:13
                                   @/home/marc/.local/share/gnome-shell/extensions/[email protected]/service/daemon.js:1132:17
Jul 09 13:16:08 MAKpc gjs[360637]: JS ERROR: TypeError: row1.message is undefined
                                   _sortMessages@/home/marc/.local/share/gnome-shell/extensions/[email protected]/service/ui/messaging.js:712:9
                                   logPrevious@/home/marc/.local/share/gnome-shell/extensions/[email protected]/service/ui/messaging.js:759:23
                                   _onSizeAllocate@/home/marc/.local/share/gnome-shell/extensions/[email protected]/service/ui/messaging.js:543:18
                                   @/home/marc/.local/share/gnome-shell/extensions/[email protected]/service/daemon.js:1132:17
Jul 09 13:16:08 MAKpc gjs[360637]: JS ERROR: TypeError: row1.message is undefined
                                   _sortMessages@/home/marc/.local/share/gnome-shell/extensions/[email protected]/service/ui/messaging.js:712:9
                                   logPrevious@/home/marc/.local/share/gnome-shell/extensions/[email protected]/service/ui/messaging.js:759:23
                                   _onSizeAllocate@/home/marc/.local/share/gnome-shell/extensions/[email protected]/service/ui/messaging.js:543:18
                                   @/home/marc/.local/share/gnome-shell/extensions/[email protected]/service/daemon.js:1132:17
Jul 09 13:16:08 MAKpc gjs[360637]: JS ERROR: TypeError: row1.message is undefined
                                   _sortMessages@/home/marc/.local/share/gnome-shell/extensions/[email protected]/service/ui/messaging.js:712:9
                                   logPrevious@/home/marc/.local/share/gnome-shell/extensions/[email protected]/service/ui/messaging.js:759:23
                                   _onSizeAllocate@/home/marc/.local/share/gnome-shell/extensions/[email protected]/service/ui/messaging.js:543:18
                                   @/home/marc/.local/share/gnome-shell/extensions/[email protected]/service/daemon.js:1132:17
Jul 09 13:16:08 MAKpc gjs[360637]: JS ERROR: TypeError: row1.message is undefined
                                   _sortMessages@/home/marc/.local/share/gnome-shell/extensions/[email protected]/service/ui/messaging.js:712:9
                                   logPrevious@/home/marc/.local/share/gnome-shell/extensions/[email protected]/service/ui/messaging.js:759:23
                                   _onSizeAllocate@/home/marc/.local/share/gnome-shell/extensions/[email protected]/service/ui/messaging.js:543:18
                                   @/home/marc/.local/share/gnome-shell/extensions/[email protected]/service/daemon.js:1132:17

It's probably unrelated though.
When switching back to a thread/contact I already opened before, it will not throw new errors, only when I switch to a new/unopened thread/contact, as said before.

[andyholmes]

I believe those most recent messages should be fixed in 29b5668, available in v40-rc1.

Reproducing the original stack trace is probably going to be very difficult, especially if it's happening where I think it is. If I'm right, we've hit a very rare thread-safety problem which is pretty difficult to do in GJS, so don't worry if you can't reproduce it again; this is the best logging we've had so far.

I'm first going to have to try and create a minimal reproducer for this problem, to confirm that our bug (because we're doing something wrong) is triggering an upstream bug that results in the crazy log-spam. Then I'll confirm it's happening where I think it is.

[ferdnyc]

• I then tried the remote keyboard, but it said "Remote keyboard on MAKoneplus 5 is not active".
• I went to my phone and checked the app to see if the remote keyboard extension is enabled or not, which it is, so I don't know why GSConnect said its not active.
• I then noticed the phone is also connected with KDE Connect on my desktop, showed fingerprints in both GSConnect and KDE Connect and compared it to the profiles on the phone. The keyboard ext was also enabled in the GSConnect profile.

To clarify, on this one: The KDE Connect Remote Keyboard is an Android input method, the app places it on the list of available inputs alongside the other soft keyboards on the device.

For the keyboard to show active (and, indeed, for it to take input) on the Linux side:

1. The plugin has to be enabled, on both sides.
2. The remote input window has to be open.
3. "KDE Connect Remote Keyboard" has to be selected as the device's current input method.
4. (And if you don't go into the app's plugin settings and uncheck "Handle remote keys only when editing", you'll also need to first tap on a field that accepts text input.)

When all of those conditions are met, you'll see a small bar at the bottom of the device screen, in place of the standard soft keyboard:

[andyholmes]

There were a lot big changes in v40 (and v41), so I'd be interested to know if you can still reproduce this bug in the latest version. I tried to work around a lot of the potential caused I figured could have been behind this.

[gnusuari0]

There were a lot big changes in v40 (and v41), so I'd be interested to know if you can still reproduce this bug in the latest version. I tried to work around a lot of the potential caused I figured could have been behind this.

I think I'm having the same issue while running the latest available in extensions.gnome.org. Ubuntu 20.04 LTS.

Syslog gets spammed. I have to SIGTERM a gjs process to stop it from filling syslog with stack traces and garbage collection errors. The paired device is a OnePlus 7 Pro with KDE Connect installed from F-Droid, version 1.14.2. All plugins are enabled, except SFTP and legacy SMS support.

Sep  6 13:34:44 host gjs[3067]: Attempting to run a JS callback during garbage collection. This is most likely caused by des
troying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked.
Sep  6 13:34:44 host org.gnome.Shell.Extensions.GSConnect[3067]: == Stack trace for context 0x5594c7a121a0 ==
Sep  6 13:34:44 host org.gnome.Shell.Extensions.GSConnect[3067]: #0   5594c7ac2500 i   /home/user/.local/share/gnome-shell/e
xtensions/[email protected]/service/daemon.js:1074 (4d937f8d178 @ 1350)
Sep  6 13:34:44 host org.gnome.Shell.Extensions.GSConnect[3067]: == Stack trace for context 0x5594c7a121a0 ==
Sep  6 13:34:44 host gjs[3067]: The offending callback was SourceFunc().
Sep  6 13:34:44 host org.gnome.Shell.Extensions.GSConnect[3067]: #0   5594c7ac2500 i   /home/user/.local/share/gnome-shell/e
xtensions/[email protected]/service/daemon.js:1074 (4d937f8d178 @ 1350)
Sep  6 13:34:44 host org.gnome.Shell.Extensions.GSConnect[3067]: == Stack trace for context 0x5594c7a121a0 ==
Sep  6 13:34:44 host gjs[3067]: Attempting to run a JS callback during garbage collection. This is most likely caused by des
troying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked.
Sep  6 13:34:44 host org.gnome.Shell.Extensions.GSConnect[3067]: #0   5594c7ac2500 i   /home/user/.local/share/gnome-shell/e
xtensions/[email protected]/service/daemon.js:1074 (4d937f8d178 @ 1350)
Sep  6 13:34:44 host gjs[3067]: The offending callback was SourceFunc().
Sep  6 13:34:44 host gjs[3067]: Attempting to run a JS callback during garbage collection. This is most likely caused by des
troying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked.
Sep  6 13:34:44 host gjs[3067]: The offending callback was SourceFunc().
Sep  6 13:34:44 host gjs[3067]: Attempting to run a JS callback during garbage collection. This is most likely caused by des
troying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked.
Sep  6 13:34:44 host gjs[3067]: The offending callback was SourceFunc().
Sep  6 13:34:44 host gjs[3067]: Attempting to run a JS callback during garbage collection. This is most likely caused by des
troying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked.
Sep  6 13:34:44 host gjs[3067]: The offending callback was SourceFunc().

[andyholmes]

Can you give any hints as to what you were doing when the problem started?

[gnusuari0]

I can say that this happens with kde connect running on the background without doing anything special or after turning on the phone, so probably when the app tries to connect to the PC. The PC is always on.

[andyholmes]

Okay. I still can't reproduce this, but I notice all the reporters seem to be using Ubuntu 20.04. I don't see any patches in gjs that seem at all related, so I'm not sure what to do here but wait for more reports :shrug:

[gnusuari0]

I'm also getting these warnings:

de set. 05 04:58:11 host gjs[3067]: JS WARNING: [/home/user/.local/share/gnome-shell/extensions/[email protected]/service/protocol/lan.js 733]: reference to undefined property "GSocketOutputStream"
de set. 05 11:27:32 host gjs[3067]: JS WARNING: [/home/user/.local/share/gnome-shell/extensions/[email protected]/service/plugins/notification.js 524]: reference to undefined property "text"

And a full stack trace with the point of failure. The previous message at 13:34 PM seems to be a continuation of this stack trace, leaving the gjs process stale. If I search in journalctl for "gsc", the next line containing it is the first one from my previous report which repeats continuously the daemon.js:1074 stack trace context.

de set. 06 10:59:23 host org.gnome.Shell.Extensions.GSConnect[3067]: #0   7ffd570fb6d0 I   /home/user/.local/share/gnome-shell/extensions/[email protected]/service/device.js:388 (4d937fdce98 @ 67)
de set. 06 10:59:23 host org.gnome.Shell.Extensions.GSConnect[3067]: #1   7ffd570fb740 I   /home/user/.local/share/gnome-shell/extensions/[email protected]/service/daemon.js:415 (4d937f8dda8 @ 440)
de set. 06 10:59:23 host org.gnome.Shell.Extensions.GSConnect[3067]: #2   7ffd570fb780 I   self-hosted:1007 (4d937ff1808 @ 398)
de set. 06 10:59:23 host org.gnome.Shell.Extensions.GSConnect[3067]: #3   5594c7ac2500 i   /home/user/.local/share/gnome-shell/extensions/[email protected]/service/daemon.js:1074 (4d937f8d178 @ 1350)
de set. 06 10:59:23 host gjs[3067]: The offending signal was activate on GSimpleAction 0x5594c7eba2d0.
de set. 06 10:59:28 host gjs[3067]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remo>
de set. 06 10:59:28 host org.gnome.Shell.Extensions.GSConnect[3067]: == Stack trace for context 0x5594c7a121a0 ==
de set. 06 10:59:28 host org.gnome.Shell.Extensions.GSConnect[3067]: #0   5594c7ac2500 i   /home/user/.local/share/gnome-shell/extensions/[email protected]/service/daemon.js:1074 (4d937f8d178 @ 1350)
de set. 06 10:59:28 host gjs[3067]: The offending callback was SourceFunc().

And today's crash:

de set. 08 12:03:51 host gjs[186561]: The offending signal was activate on GSimpleAction 0x559381e41800.
de set. 08 12:03:51 host org.gnome.Shell.Extensions.GSConnect[186561]: == Stack trace for context 0x5593816e11a0 ==
de set. 08 12:03:51 host org.gnome.Shell.Extensions.GSConnect[186561]: #0   7ffdfc337390 I   /home/user/.local/share/gnome-shell/extensions/[email protected]/service/device.js:388 (39104bddce98 @ 67)
de set. 08 12:03:51 host org.gnome.Shell.Extensions.GSConnect[186561]: #1   7ffdfc337400 I   /home/user/.local/share/gnome-shell/extensions/[email protected]/service/daemon.js:415 (39104bd8dda8 @ 440)
de set. 08 12:03:51 host org.gnome.Shell.Extensions.GSConnect[186561]: #2   7ffdfc337440 I   self-hosted:1007 (39104bdf1808 @ 398)
de set. 08 12:03:51 host org.gnome.Shell.Extensions.GSConnect[186561]: #3   559381791500 i   /home/user/.local/share/gnome-shell/extensions/[email protected]/service/daemon.js:1074 (39104bd8d178 @ 1350)
de set. 08 12:03:56 host gjs[186561]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or re>
de set. 08 12:03:56 host org.gnome.Shell.Extensions.GSConnect[186561]: == Stack trace for context 0x5593816e11a0 ==
de set. 08 12:03:56 host org.gnome.Shell.Extensions.GSConnect[186561]: #0   559381791500 i   /home/user/.local/share/gnome-shell/extensions/[email protected]/service/daemon.js:1074 (39104bd8d178 @ 1350)
de set. 08 12:03:56 host gjs[186561]: The offending callback was SourceFunc().
de set. 08 12:04:52 host gjs[186561]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or re>
de set. 08 12:04:52 host org.gnome.Shell.Extensions.GSConnect[186561]: == Stack trace for context 0x5593816e11a0 ==
de set. 08 12:04:52 host org.gnome.Shell.Extensions.GSConnect[186561]: #0   559381791500 i   /home/user/.local/share/gnome-shell/extensions/[email protected]/service/daemon.js:1074 (39104bd8d178 @ 1350)

It continues repeating the stack trace context of #0... daemon.js:1074.

[andyholmes]

I'm also getting these warnings:
de set. 05 04:58:11 host gjs[3067]: JS WARNING: [/home/user/.local/share/gnome-shell/extensions/[email protected]/service/protocol/lan.js 733]: reference to undefined property "GSocketOutputStream"

This one is deeper in gjs/gobject-introspection so there's not much I can do about this I think. Should be harmless though.

de set. 05 11:27:32 host gjs[3067]: JS WARNING: [/home/user/.local/share/gnome-shell/extensions/[email protected]/service/plugins/notification.js 524]: reference to undefined property "text"

I can add a check for this, but it's also harmless. It will simply result in undefined being coerced to the string "undefined".

de set. 08 12:03:51 host gjs[186561]: The offending signal was activate on GSimpleAction 0x559381e41800.
de set. 08 12:03:51 host org.gnome.Shell.Extensions.GSConnect[186561]: == Stack trace for context 0x5593816e11a0 ==
de set. 08 12:03:51 host org.gnome.Shell.Extensions.GSConnect[186561]: #0   7ffdfc337390 I   /home/user/.local/share/gnome-shell/extensions/[email protected]/service/device.js:388 (39104bddce98 @ 67)
de set. 08 12:03:51 host org.gnome.Shell.Extensions.GSConnect[186561]: #1   7ffdfc337400 I   /home/user/.local/share/gnome-shell/extensions/[email protected]/service/daemon.js:415 (39104bd8dda8 @ 440)
de set. 08 12:03:51 host org.gnome.Shell.Extensions.GSConnect[186561]: #2   7ffdfc337440 I   self-hosted:1007 (39104bdf1808 @ 398)
de set. 08 12:03:51 host org.gnome.Shell.Extensions.GSConnect[186561]: #3   559381791500 i   /home/user/.local/share/gnome-shell/extensions/[email protected]/service/daemon.js:1074 (39104bd8d178 @ 1350)

Ah, now I get it! Here's what happened (disclaimer: nerd stuff):

• The reconnect timer uses a GSource that periodically calls a GSourceFunc.
• The GSourceFunc activates a GAction which emits a signal to execute the action.
• When the GSourceFunc returns, a garbage collection sweep is triggered.
• In some rare case, the GAction signal is emitted at the same time the GC sweep is happening

In any case, this code path has changed in master and no longer involves activating a GAction. If you like you can try running the latest from master to confirm it's fixed (Instructions):

[email protected]

[ferdnyc]

• In some rare case, the GAction signal is emitted at the same time the GC sweep is happening

Based on the frequency in some of these reports, _define_ "rare"? :wink: (Sounds to me like Ubuntu might be using loaded dice, anyway.)

[andyholmes]

Well, "rare" as in I've never been able to reproduce it myself, this callback is invoked every 5 seconds, and during GUADEC I got some numbers for installs of about 50k (the other train left at 9am, moving at 40 mph :wink:)

[gnusuari0]

I haven't got any issue since I installed the zip you provided.

[andyholmes]

That's great news, thanks for testing and confirming!

[andyholmes]

Closing since the fix has been released in v42.