Random crashes - JSAPI call during GC

When typing, Ibus-avro crashes randomly. This happened on Kali Linux 2020.4. I also encountered this problem on Ubuntu 20.04. After it crashes, switching to “EN” and then switching back doesn’t works. But if I run ibus restart then it works. But it’s kinda annoying.

Here’s the output after running ibus-daemon -r -v

100 32 0
100 32 1073741824
117 22 0
105 23 0
117 22 1073741824
105 23 1073741824
98 48 0
104 35 0
98 48 1073741824
97 30 0
104 35 1073741824
97 30 1073741824
98 48 0
98 48 1073741824
101 18 0
101 18 1073741824
32 57 0
32 57 1073741824
65505 42 0
65505 42 1073741825
65505 42 0
68 32 1
68 32 1073741825
65505 42 1073741825
105 23 0
105 23 1073741824
107 37 0
107 37 1073741824
108 38 0
108 38 1073741824
101 18 0
101 18 1073741824
65288 14 0
65288 14 1073741824
65288 14 0
65288 14 1073741824
65288 14 0
65288 14 1073741824
65288 14 0
65288 14 1073741824
65288 14 0
65288 14 1073741824
116 20 0
116 20 1073741824
65505 42 0
65505 42 1073741825
65288 14 0
65288 14 1073741824
32 57 0
32 57 1073741824
116 20 0
116 20 1073741824
65505 42 0
79 24 1
73 23 1
79 24 1073741825
65505 42 1073741825
105 23 1073741824
114 19 0
114 19 1073741824
105 23 0
105 23 1073741824
32 57 0
32 57 1073741824
107 37 0
111 24 0
107 37 1073741824
111 24 1073741824
114 19 0
114 19 1073741824
97 30 0
97 30 1073741824
32 57 0
32 57 1073741824
122 44 0
97 30 0
122 44 1073741824
121 21 0
97 30 1073741824
121 21 1073741824
46 52 0
32 57 0
46 52 1073741824
32 57 1073741824
101 18 0
101 18 1073741824
107 37 0
107 37 1073741824
65288 14 0
65288 14 1073741824
65288 14 0
65288 14 1073741824
112 25 0
112 25 1073741824
114 19 0
114 19 1073741824
111 24 0

(gjs:10663): Gjs-CRITICAL **: 15:20:09.895: 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.

(gjs:10663): Gjs-CRITICAL **: 15:20:09.895: The offending signal was process-key-event on IBusEngine 0x55db8c7290b0.
== Stack trace for context 0x55db8c5041a0 ==
#0   55db8c6c6f40 i   /usr/share/ibus-avro/main-gjs.js:422 (346ccac846a0 @ 1506)

(gjs:10663): Gjs-CRITICAL **: 15:20:09.948: 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.

(gjs:10663): Gjs-CRITICAL **: 15:20:09.948: The offending signal was process-key-event on IBusEngine 0x55db8c7290b0.
== Stack trace for context 0x55db8c5041a0 ==
#0   55db8c6c6f40 i   /usr/share/ibus-avro/main-gjs.js:422 (346ccac846a0 @ 1506)

(gjs:10663): Gjs-CRITICAL **: 15:20:10.031: 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.

(gjs:10663): Gjs-CRITICAL **: 15:20:10.031: The offending signal was process-key-event on IBusEngine 0x55db8c7290b0.
== Stack trace for context 0x55db8c5041a0 ==
#0   55db8c6c6f40 i   /usr/share/ibus-avro/main-gjs.js:422 (346ccac846a0 @ 1506)

(gjs:10663): Gjs-CRITICAL **: 15:20:10.336: 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.

(gjs:10663): Gjs-CRITICAL **: 15:20:10.336: The offending signal was process-key-event on IBusEngine 0x55db8c7290b0.
== Stack trace for context 0x55db8c5041a0 ==
#0   55db8c6c6f40 i   /usr/share/ibus-avro/main-gjs.js:422 (346ccac846a0 @ 1506)

(gjs:10663): Gjs-CRITICAL **: 15:20:10.382: 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.

(gjs:10663): Gjs-CRITICAL **: 15:20:10.383: The offending signal was process-key-event on IBusEngine 0x55db8c7290b0.
== Stack trace for context 0x55db8c5041a0 ==
#0   55db8c6c6f40 i   /usr/share/ibus-avro/main-gjs.js:422 (346ccac846a0 @ 1506)

(gjs:10663): Gjs-CRITICAL **: 15:20:10.478: 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.

(gjs:10663): Gjs-CRITICAL **: 15:20:10.478: The offending signal was process-key-event on IBusEngine 0x55db8c7290b0.
== Stack trace for context 0x55db8c5041a0 ==
#0   55db8c6c6f40 i   /usr/share/ibus-avro/main-gjs.js:422 (346ccac846a0 @ 1506)

(gjs:10663): Gjs-CRITICAL **: 15:20:10.541: 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.

(gjs:10663): Gjs-CRITICAL **: 15:20:10.541: The offending signal was process-key-event on IBusEngine 0x55db8c7290b0.
== Stack trace for context 0x55db8c5041a0 ==
#0   55db8c6c6f40 i   /usr/share/ibus-avro/main-gjs.js:422 (346ccac846a0 @ 1506)

(gjs:10663): Gjs-CRITICAL **: 15:20:11.212: 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.

(gjs:10663): Gjs-CRITICAL **: 15:20:11.212: The offending signal was process-key-event on IBusEngine 0x55db8c7290b0.
== Stack trace for context 0x55db8c5041a0 ==
#0   55db8c6c6f40 i   /usr/share/ibus-avro/main-gjs.js:422 (346ccac846a0 @ 1506)

(gjs:10663): Gjs-CRITICAL **: 15:20:11.325: 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.

(gjs:10663): Gjs-CRITICAL **: 15:20:11.325: The offending signal was process-key-event on IBusEngine 0x55db8c7290b0.
== Stack trace for context 0x55db8c5041a0 ==
#0   55db8c6c6f40 i   /usr/share/ibus-avro/main-gjs.js:422 (346ccac846a0 @ 1506)

(gjs:10663): Gjs-CRITICAL **: 15:20:11.813: 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.

(gjs:10663): Gjs-CRITICAL **: 15:20:11.813: The offending signal was process-key-event on IBusEngine 0x55db8c7290b0.
== Stack trace for context 0x55db8c5041a0 ==
#0   55db8c6c6f40 i   /usr/share/ibus-avro/main-gjs.js:422 (346ccac846a0 @ 1506)

(gjs:10663): Gjs-CRITICAL **: 15:20:11.860: 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.

(gjs:10663): Gjs-CRITICAL **: 15:20:11.860: The offending signal was process-key-event on IBusEngine 0x55db8c7290b0.
== Stack trace for context 0x55db8c5041a0 ==
#0   55db8c6c6f40 i   /usr/share/ibus-avro/main-gjs.js:422 (346ccac846a0 @ 1506)

(gjs:10663): Gjs-CRITICAL **: 15:20:12.210: 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.

(gjs:10663): Gjs-CRITICAL **: 15:20:12.210: The offending signal was process-key-event on IBusEngine 0x55db8c7290b0.
== Stack trace for context 0x55db8c5041a0 ==
#0   55db8c6c6f40 i   /usr/share/ibus-avro/main-gjs.js:422 (346ccac846a0 @ 1506)

(gjs:10663): Gjs-CRITICAL **: 15:20:12.345: 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.

(gjs:10663): Gjs-CRITICAL **: 15:20:12.345: The offending signal was focus-out on IBusEngine 0x55db8c7290b0.
== Stack trace for context 0x55db8c5041a0 ==
#0   55db8c6c6f40 i   /usr/share/ibus-avro/main-gjs.js:422 (346ccac846a0 @ 1506)

(gjs:10663): Gjs-CRITICAL **: 15:20:12.356: 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.

(gjs:10663): Gjs-CRITICAL **: 15:20:12.356: The offending signal was focus-in on IBusEngine 0x55db8c7290b0.
== Stack trace for context 0x55db8c5041a0 ==
#0   55db8c6c6f40 i   /usr/share/ibus-avro/main-gjs.js:422 (346ccac846a0 @ 1506)

(gjs:10663): Gjs-CRITICAL **: 15:20:12.362: 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.

(gjs:10663): Gjs-CRITICAL **: 15:20:12.362: The offending signal was focus-out on IBusEngine 0x55db8c7290b0.
== Stack trace for context 0x55db8c5041a0 ==
#0   55db8c6c6f40 i   /usr/share/ibus-avro/main-gjs.js:422 (346ccac846a0 @ 1506)

(gjs:10663): Gjs-CRITICAL **: 15:20:12.362: 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.

(gjs:10663): Gjs-CRITICAL **: 15:20:12.362: The offending signal was focus-in on IBusEngine 0x55db8c7290b0.
== Stack trace for context 0x55db8c5041a0 ==
#0   55db8c6c6f40 i   /usr/share/ibus-avro/main-gjs.js:422 (346ccac846a0 @ 1506)

(gjs:10663): Gjs-CRITICAL **: 15:20:12.365: 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.

(gjs:10663): Gjs-CRITICAL **: 15:20:12.365: The offending signal was focus-out on IBusEngine 0x55db8c7290b0.
== Stack trace for context 0x55db8c5041a0 ==
#0   55db8c6c6f40 i   /usr/share/ibus-avro/main-gjs.js:422 (346ccac846a0 @ 1506)

(gjs:10663): Gjs-CRITICAL **: 15:20:12.368: 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.

(gjs:10663): Gjs-CRITICAL **: 15:20:12.368: The offending signal was focus-in on IBusEngine 0x55db8c7290b0.
== Stack trace for context 0x55db8c5041a0 ==
#0   55db8c6c6f40 i   /usr/share/ibus-avro/main-gjs.js:422 (346ccac846a0 @ 1506)

(gjs:10663): Gjs-CRITICAL **: 15:20:12.371: 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.

(gjs:10663): Gjs-CRITICAL **: 15:20:12.371: The offending signal was focus-out on IBusEngine 0x55db8c7290b0.
== Stack trace for context 0x55db8c5041a0 ==
#0   55db8c6c6f40 i   /usr/share/ibus-avro/main-gjs.js:422 (346ccac846a0 @ 1506)

(gjs:10663): Gjs-CRITICAL **: 15:20:12.374: 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.

(gjs:10663): Gjs-CRITICAL **: 15:20:12.374: The offending signal was focus-in on IBusEngine 0x55db8c7290b0.
== Stack trace for context 0x55db8c5041a0 ==
#0   55db8c6c6f40 i   /usr/share/ibus-avro/main-gjs.js:422 (346ccac846a0 @ 1506)

(gjs:10663): Gjs-CRITICAL **: 15:20:12.377: 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.

(gjs:10663): Gjs-CRITICAL **: 15:20:12.377: The offending signal was focus-out on IBusEngine 0x55db8c7290b0.
== Stack trace for context 0x55db8c5041a0 ==
#0   55db8c6c6f40 i   /usr/share/ibus-avro/main-gjs.js:422 (346ccac846a0 @ 1506)

(gjs:10663): Gjs-CRITICAL **: 15:20:12.377: 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.

(gjs:10663): Gjs-CRITICAL **: 15:20:12.377: The offending signal was focus-in on IBusEngine 0x55db8c7290b0.
== Stack trace for context 0x55db8c5041a0 ==
#0   55db8c6c6f40 i   /usr/share/ibus-avro/main-gjs.js:422 (346ccac846a0 @ 1506)

(gjs:10663): Gjs-CRITICAL **: 15:20:12.396: 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.

(gjs:10663): Gjs-CRITICAL **: 15:20:12.396: The offending signal was focus-out on IBusEngine 0x55db8c7290b0.
== Stack trace for context 0x55db8c5041a0 ==
#0   55db8c6c6f40 i   /usr/share/ibus-avro/main-gjs.js:422 (346ccac846a0 @ 1506)

(gjs:10663): Gjs-CRITICAL **: 15:20:12.402: 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.

(gjs:10663): Gjs-CRITICAL **: 15:20:12.402: The offending signal was focus-in on IBusEngine 0x55db8c7290b0.
== Stack trace for context 0x55db8c5041a0 ==
#0   55db8c6c6f40 i   /usr/share/ibus-avro/main-gjs.js:422 (346ccac846a0 @ 1506)

(gjs:10663): Gjs-CRITICAL **: 15:20:12.402: 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.

(gjs:10663): Gjs-CRITICAL **: 15:20:12.403: The offending signal was focus-out on IBusEngine 0x55db8c7290b0.
== Stack trace for context 0x55db8c5041a0 ==
#0   55db8c6c6f40 i   /usr/share/ibus-avro/main-gjs.js:422 (346ccac846a0 @ 1506)

(gjs:10663): Gjs-CRITICAL **: 15:20:12.403: 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.

(gjs:10663): Gjs-CRITICAL **: 15:20:12.403: The offending signal was focus-in on IBusEngine 0x55db8c7290b0.
== Stack trace for context 0x55db8c5041a0 ==
#0   55db8c6c6f40 i   /usr/share/ibus-avro/main-gjs.js:422 (346ccac846a0 @ 1506)

(gjs:10663): Gjs-CRITICAL **: 15:20:12.456: 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.

(gjs:10663): Gjs-CRITICAL **: 15:20:12.456: The offending signal was focus-out on IBusEngine 0x55db8c7290b0.
== Stack trace for context 0x55db8c5041a0 ==
#0   55db8c6c6f40 i   /usr/share/ibus-avro/main-gjs.js:422 (346ccac846a0 @ 1506)

(gjs:10663): Gjs-CRITICAL **: 15:20:12.457: 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.

(gjs:10663): Gjs-CRITICAL **: 15:20:12.457: The offending signal was focus-in on IBusEngine 0x55db8c7290b0.
== Stack trace for context 0x55db8c5041a0 ==
#0   55db8c6c6f40 i   /usr/share/ibus-avro/main-gjs.js:422 (346ccac846a0 @ 1506)

(gjs:10663): Gjs-CRITICAL **: 15:20:12.457: 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.

(gjs:10663): Gjs-CRITICAL **: 15:20:12.458: The offending signal was focus-out on IBusEngine 0x55db8c7290b0.
== Stack trace for context 0x55db8c5041a0 ==
#0   55db8c6c6f40 i   /usr/share/ibus-avro/main-gjs.js:422 (346ccac846a0 @ 1506)

(gjs:10663): Gjs-CRITICAL **: 15:20:12.459: 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.

(gjs:10663): Gjs-CRITICAL **: 15:20:12.459: The offending signal was focus-in on IBusEngine 0x55db8c7290b0.
== Stack trace for context 0x55db8c5041a0 ==
#0   55db8c6c6f40 i   /usr/share/ibus-avro/main-gjs.js:422 (346ccac846a0 @ 1506)

(gjs:10663): Gjs-CRITICAL **: 15:20:12.460: 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.

(gjs:10663): Gjs-CRITICAL **: 15:20:12.460: The offending signal was focus-out on IBusEngine 0x55db8c7290b0.
== Stack trace for context 0x55db8c5041a0 ==
#0   55db8c6c6f40 i   /usr/share/ibus-avro/main-gjs.js:422 (346ccac846a0 @ 1506)

(gjs:10663): Gjs-CRITICAL **: 15:20:12.461: 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.

(gjs:10663): Gjs-CRITICAL **: 15:20:12.461: The offending signal was focus-in on IBusEngine 0x55db8c7290b0.
== Stack trace for context 0x55db8c5041a0 ==
#0   55db8c6c6f40 i   /usr/share/ibus-avro/main-gjs.js:422 (346ccac846a0 @ 1506)

(gjs:10663): Gjs-CRITICAL **: 15:20:12.461: 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.

(gjs:10663): Gjs-CRITICAL **: 15:20:12.461: The offending signal was focus-out on IBusEngine 0x55db8c7290b0.
== Stack trace for context 0x55db8c5041a0 ==
#0   55db8c6c6f40 i   /usr/share/ibus-avro/main-gjs.js:422 (346ccac846a0 @ 1506)

(gjs:10663): Gjs-CRITICAL **: 15:20:12.461: 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.

(gjs:10663): Gjs-CRITICAL **: 15:20:12.461: The offending signal was focus-in on IBusEngine 0x55db8c7290b0.
== Stack trace for context 0x55db8c5041a0 ==
#0   55db8c6c6f40 i   /usr/share/ibus-avro/main-gjs.js:422 (346ccac846a0 @ 1506)

(gjs:10663): Gjs-CRITICAL **: 15:20:12.471: 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.

(gjs:10663): Gjs-CRITICAL **: 15:20:12.471: The offending signal was focus-out on IBusEngine 0x55db8c7290b0.
== Stack trace for context 0x55db8c5041a0 ==
#0   55db8c6c6f40 i   /usr/share/ibus-avro/main-gjs.js:422 (346ccac846a0 @ 1506)

(gjs:10663): Gjs-CRITICAL **: 15:20:12.471: 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.

(gjs:10663): Gjs-CRITICAL **: 15:20:12.472: The offending signal was focus-in on IBusEngine 0x55db8c7290b0.
== Stack trace for context 0x55db8c5041a0 ==
#0   55db8c6c6f40 i   /usr/share/ibus-avro/main-gjs.js:422 (346ccac846a0 @ 1506)

(gjs:10663): Gjs-CRITICAL **: 15:20:12.507: 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.

(gjs:10663): Gjs-CRITICAL **: 15:20:12.507: The offending signal was focus-out on IBusEngine 0x55db8c7290b0.
== Stack trace for context 0x55db8c5041a0 ==
#0   55db8c6c6f40 i   /usr/share/ibus-avro/main-gjs.js:422 (346ccac846a0 @ 1506)

(gjs:10663): Gjs-CRITICAL **: 15:20:12.508: 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.

(gjs:10663): Gjs-CRITICAL **: 15:20:12.508: The offending signal was focus-in on IBusEngine 0x55db8c7290b0.
== Stack trace for context 0x55db8c5041a0 ==
#0   55db8c6c6f40 i   /usr/share/ibus-avro/main-gjs.js:422 (346ccac846a0 @ 1506)

(gjs:10663): Gjs-CRITICAL **: 15:20:25.667: 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.

(gjs:10663): Gjs-CRITICAL **: 15:20:25.667: The offending signal was focus-out on IBusEngine 0x55db8c7290b0.
== Stack trace for context 0x55db8c5041a0 ==
#0   55db8c6c6f40 i   /usr/share/ibus-avro/main-gjs.js:422 (346ccac846a0 @ 1506)

(gjs:10663): Gjs-CRITICAL **: 15:20:25.670: 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.

(gjs:10663): Gjs-CRITICAL **: 15:20:25.670: The offending signal was focus-in on IBusEngine 0x55db8c7290b0.
== Stack trace for context 0x55db8c5041a0 ==
#0   55db8c6c6f40 i   /usr/share/ibus-avro/main-gjs.js:422 (346ccac846a0 @ 1506)

(gjs:10663): Gjs-CRITICAL **: 15:20:25.679: 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.

(gjs:10663): Gjs-CRITICAL **: 15:20:25.679: The offending signal was focus-out on IBusEngine 0x55db8c7290b0.
== Stack trace for context 0x55db8c5041a0 ==
#0   55db8c6c6f40 i   /usr/share/ibus-avro/main-gjs.js:422 (346ccac846a0 @ 1506)

(gjs:10663): Gjs-CRITICAL **: 15:20:25.680: 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.

(gjs:10663): Gjs-CRITICAL **: 15:20:25.680: The offending signal was focus-in on IBusEngine 0x55db8c7290b0.
== Stack trace for context 0x55db8c5041a0 ==
#0   55db8c6c6f40 i   /usr/share/ibus-avro/main-gjs.js:422 (346ccac846a0 @ 1506)

(gjs:10663): Gjs-CRITICAL **: 15:20:25.684: 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.

(gjs:10663): Gjs-CRITICAL **: 15:20:25.684: The offending signal was focus-out on IBusEngine 0x55db8c7290b0.
== Stack trace for context 0x55db8c5041a0 ==
#0   55db8c6c6f40 i   /usr/share/ibus-avro/main-gjs.js:422 (346ccac846a0 @ 1506)

(gjs:10663): Gjs-CRITICAL **: 15:20:25.684: 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.

(gjs:10663): Gjs-CRITICAL **: 15:20:25.684: The offending signal was focus-in on IBusEngine 0x55db8c7290b0.
== Stack trace for context 0x55db8c5041a0 ==
#0   55db8c6c6f40 i   /usr/share/ibus-avro/main-gjs.js:422 (346ccac846a0 @ 1506)

(gjs:10663): Gjs-CRITICAL **: 15:20:25.709: 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.

(gjs:10663): Gjs-CRITICAL **: 15:20:25.709: The offending signal was focus-out on IBusEngine 0x55db8c7290b0.
== Stack trace for context 0x55db8c5041a0 ==
#0   55db8c6c6f40 i   /usr/share/ibus-avro/main-gjs.js:422 (346ccac846a0 @ 1506)

(gjs:10663): Gjs-CRITICAL **: 15:20:25.710: 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.

(gjs:10663): Gjs-CRITICAL **: 15:20:25.710: The offending signal was focus-in on IBusEngine 0x55db8c7290b0.
== Stack trace for context 0x55db8c5041a0 ==
#0   55db8c6c6f40 i   /usr/share/ibus-avro/main-gjs.js:422 (346ccac846a0 @ 1506)

(gjs:10663): Gjs-CRITICAL **: 15:20:26.624: 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.

(gjs:10663): Gjs-CRITICAL **: 15:20:26.624: The offending signal was focus-out on IBusEngine 0x55db8c7290b0.
== Stack trace for context 0x55db8c5041a0 ==
#0   55db8c6c6f40 i   /usr/share/ibus-avro/main-gjs.js:422 (346ccac846a0 @ 1506)

(gjs:10663): Gjs-CRITICAL **: 15:20:26.629: 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.

(gjs:10663): Gjs-CRITICAL **: 15:20:26.629: The offending signal was focus-in on IBusEngine 0x55db8c7290b0.
== Stack trace for context 0x55db8c5041a0 ==
#0   55db8c6c6f40 i   /usr/share/ibus-avro/main-gjs.js:422 (346ccac846a0 @ 1506)

(gjs:10663): Gjs-CRITICAL **: 15:20:26.629: 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.

(gjs:10663): Gjs-CRITICAL **: 15:20:26.629: The offending signal was focus-out on IBusEngine 0x55db8c7290b0.
== Stack trace for context 0x55db8c5041a0 ==
#0   55db8c6c6f40 i   /usr/share/ibus-avro/main-gjs.js:422 (346ccac846a0 @ 1506)

(gjs:10663): Gjs-CRITICAL **: 15:20:26.629: 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.

(gjs:10663): Gjs-CRITICAL **: 15:20:26.629: The offending signal was focus-in on IBusEngine 0x55db8c7290b0.
== Stack trace for context 0x55db8c5041a0 ==
#0   55db8c6c6f40 i   /usr/share/ibus-avro/main-gjs.js:422 (346ccac846a0 @ 1506)

(gjs:10663): Gjs-CRITICAL **: 15:20:26.630: 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.

(gjs:10663): Gjs-CRITICAL **: 15:20:26.630: The offending signal was focus-out on IBusEngine 0x55db8c7290b0.
== Stack trace for context 0x55db8c5041a0 ==
#0   55db8c6c6f40 i   /usr/share/ibus-avro/main-gjs.js:422 (346ccac846a0 @ 1506)

(gjs:10663): Gjs-CRITICAL **: 15:20:26.630: 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.

(gjs:10663): Gjs-CRITICAL **: 15:20:26.630: The offending signal was focus-in on IBusEngine 0x55db8c7290b0.
== Stack trace for context 0x55db8c5041a0 ==
#0   55db8c6c6f40 i   /usr/share/ibus-avro/main-gjs.js:422 (346ccac846a0 @ 1506)

(gjs:10663): Gjs-CRITICAL **: 15:20:27.012: 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.

(gjs:10663): Gjs-CRITICAL **: 15:20:27.012: The offending signal was focus-out on IBusEngine 0x55db8c7290b0.
== Stack trace for context 0x55db8c5041a0 ==
#0   55db8c6c6f40 i   /usr/share/ibus-avro/main-gjs.js:422 (346ccac846a0 @ 1506)

(gjs:10663): Gjs-CRITICAL **: 15:20:27.012: 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.

(gjs:10663): Gjs-CRITICAL **: 15:20:27.012: The offending signal was focus-in on IBusEngine 0x55db8c7290b0.
== Stack trace for context 0x55db8c5041a0 ==
#0   55db8c6c6f40 i   /usr/share/ibus-avro/main-gjs.js:422 (346ccac846a0 @ 1506)

(gjs:10663): Gjs-CRITICAL **: 15:20:27.432: 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.

(gjs:10663): Gjs-CRITICAL **: 15:20:27.432: The offending signal was process-key-event on IBusEngine 0x55db8c7290b0.
== Stack trace for context 0x55db8c5041a0 ==
#0   55db8c6c6f40 i   /usr/share/ibus-avro/main-gjs.js:422 (346ccac846a0 @ 1506)

(gjs:10663): Gjs-CRITICAL **: 15:20:27.517: 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.

(gjs:10663): Gjs-CRITICAL **: 15:20:27.517: The offending signal was process-key-event on IBusEngine 0x55db8c7290b0.
== Stack trace for context 0x55db8c5041a0 ==
#0   55db8c6c6f40 i   /usr/share/ibus-avro/main-gjs.js:422 (346ccac846a0 @ 1506)

(gjs:10663): Gjs-CRITICAL **: 15:20:27.542: 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.

(gjs:10663): Gjs-CRITICAL **: 15:20:27.542: The offending signal was process-key-event on IBusEngine 0x55db8c7290b0.
== Stack trace for context 0x55db8c5041a0 ==
#0   55db8c6c6f40 i   /usr/share/ibus-avro/main-gjs.js:422 (346ccac846a0 @ 1506)

(gjs:10663): Gjs-CRITICAL **: 15:20:27.579: 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.

(gjs:10663): Gjs-CRITICAL **: 15:20:27.579: The offending signal was process-key-event on IBusEngine 0x55db8c7290b0.
== Stack trace for context 0x55db8c5041a0 ==
#0   55db8c6c6f40 i   /usr/share/ibus-avro/main-gjs.js:422 (346ccac846a0 @ 1506)

(gjs:10663): Gjs-CRITICAL **: 15:20:27.901: 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.

(gjs:10663): Gjs-CRITICAL **: 15:20:27.901: The offending signal was process-key-event on IBusEngine 0x55db8c7290b0.
== Stack trace for context 0x55db8c5041a0 ==
#0   55db8c6c6f40 i   /usr/share/ibus-avro/main-gjs.js:422 (346ccac846a0 @ 1506)

(gjs:10663): Gjs-CRITICAL **: 15:20:27.922: 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.

(gjs:10663): Gjs-CRITICAL **: 15:20:27.922: The offending signal was focus-out on IBusEngine 0x55db8c7290b0.
== Stack trace for context 0x55db8c5041a0 ==
#0   55db8c6c6f40 i   /usr/share/ibus-avro/main-gjs.js:422 (346ccac846a0 @ 1506)

(gjs:10663): Gjs-CRITICAL **: 15:20:27.925: 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.

(gjs:10663): Gjs-CRITICAL **: 15:20:27.925: The offending signal was focus-in on IBusEngine 0x55db8c7290b0.
== Stack trace for context 0x55db8c5041a0 ==
#0   55db8c6c6f40 i   /usr/share/ibus-avro/main-gjs.js:422 (346ccac846a0 @ 1506)

(gjs:10663): Gjs-CRITICAL **: 15:20:27.930: 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.

(gjs:10663): Gjs-CRITICAL **: 15:20:27.930: The offending signal was focus-out on IBusEngine 0x55db8c7290b0.
== Stack trace for context 0x55db8c5041a0 ==
#0   55db8c6c6f40 i   /usr/share/ibus-avro/main-gjs.js:422 (346ccac846a0 @ 1506)

(gjs:10663): Gjs-CRITICAL **: 15:20:27.934: 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.

(gjs:10663): Gjs-CRITICAL **: 15:20:27.934: The offending signal was focus-in on IBusEngine 0x55db8c7290b0.
== Stack trace for context 0x55db8c5041a0 ==
#0   55db8c6c6f40 i   /usr/share/ibus-avro/main-gjs.js:422 (346ccac846a0 @ 1506)

(gjs:10663): Gjs-CRITICAL **: 15:20:27.934: 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.

(gjs:10663): Gjs-CRITICAL **: 15:20:27.934: The offending signal was focus-out on IBusEngine 0x55db8c7290b0.
== Stack trace for context 0x55db8c5041a0 ==
#0   55db8c6c6f40 i   /usr/share/ibus-avro/main-gjs.js:422 (346ccac846a0 @ 1506)

(gjs:10663): Gjs-CRITICAL **: 15:20:27.937: 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.

(gjs:10663): Gjs-CRITICAL **: 15:20:27.937: The offending signal was focus-in on IBusEngine 0x55db8c7290b0.
== Stack trace for context 0x55db8c5041a0 ==
#0   55db8c6c6f40 i   /usr/share/ibus-avro/main-gjs.js:422 (346ccac846a0 @ 1506)

(gjs:10663): Gjs-CRITICAL **: 15:20:28.707: 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.

(gjs:10663): Gjs-CRITICAL **: 15:20:28.707: The offending signal was focus-out on IBusEngine 0x55db8c7290b0.
== Stack trace for context 0x55db8c5041a0 ==
#0   55db8c6c6f40 i   /usr/share/ibus-avro/main-gjs.js:422 (346ccac846a0 @ 1506)

(gjs:10663): Gjs-CRITICAL **: 15:20:28.708: 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.

(gjs:10663): Gjs-CRITICAL **: 15:20:28.708: The offending signal was focus-in on IBusEngine 0x55db8c7290b0.
== Stack trace for context 0x55db8c5041a0 ==
#0   55db8c6c6f40 i   /usr/share/ibus-avro/main-gjs.js:422 (346ccac846a0 @ 1506)

(gjs:10663): Gjs-CRITICAL **: 15:20:28.710: 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.

(gjs:10663): Gjs-CRITICAL **: 15:20:28.710: The offending signal was focus-out on IBusEngine 0x55db8c7290b0.
== Stack trace for context 0x55db8c5041a0 ==
#0   55db8c6c6f40 i   /usr/share/ibus-avro/main-gjs.js:422 (346ccac846a0 @ 1506)

(gjs:10663): Gjs-CRITICAL **: 15:20:28.711: 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.

(gjs:10663): Gjs-CRITICAL **: 15:20:28.711: The offending signal was focus-in on IBusEngine 0x55db8c7290b0.
== Stack trace for context 0x55db8c5041a0 ==
#0   55db8c6c6f40 i   /usr/share/ibus-avro/main-gjs.js:422 (346ccac846a0 @ 1506)

(gjs:10663): Gjs-CRITICAL **: 15:20:28.719: 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.

(gjs:10663): Gjs-CRITICAL **: 15:20:28.719: The offending signal was focus-out on IBusEngine 0x55db8c7290b0.
== Stack trace for context 0x55db8c5041a0 ==
#0   55db8c6c6f40 i   /usr/share/ibus-avro/main-gjs.js:422 (346ccac846a0 @ 1506)

[sarim]

This seems like the same or similar issue to #143 and #151 . I couldn’t debug those as those didn’t have relevant information.

Seems like the issue comes from gjs’s GC running at awkward moments (for lack of a better scientific word) and making the JavaScript context invalid/frozen/hanged. It doesn’t crash, which is a bad thing here. If a ibus engine process crashes normally ibus will try to restart it, but in this case the context is in a invalid state but the process is running.

This comes up in a bit of googling https://www.phoronix.com/scan.php?page=news_item&px=GNOME-Shell-Memory-Leak-Fix . More information is in the links inside the article.

So they changes GC behavior of gjs, its a total guess but maybe that caused the issue.

Also the problem is kinda hard to reproduce, as it doesn’t happen 100% of the time.

[sarim]

Unfortunately I couldn’t manage to find the time to investigate it further. But I’m not super confident about the previous commit. I do have another quick fix idea, and I’ll try to implement it. If that helps then I’ll do a minor release. Then it can be updated in debian/ubuntu repos.