Crash of gnome shell potentially from "JS ERROR: too much recursion" from app indicators
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-shell-extension-appindicator (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
What Happened:
1) Have gnome-shell-
2) The only running app using the indicator was charmtimetracker ( https:/
3) At some point usually within 1-2 days of office usage gnome shell crashes
4) Notice "JS ERROR: too much recursion" and then a stacktrace coming from appindicator extension in journalctl
What I expected to happen:
For gnome-shell not to crash :-)
Full logs:
- Recursion warnings - https:/
- Stack trace - https:/
Short Summary of Logs:
=== First sign of incoming crash ===
Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: JS ERROR: too much recursion
=== This continues many times, last instance is like this ===
Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: JS ERROR: Exception in callback for signal: child-added: too much recursion
=== Then there is a stacktrace (shortened repeats) ===
Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: 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.
Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: The offending signal was notify on StLabel 0x5615bd3eee80.
Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: == Stack trace for context 0x56159bbee930 ==
Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: #0 7ffca7535bb0 b /<email address hidden>
Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: #1 7ffca7535c80 b /<email address hidden>
Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: #2 5615a5c69340 i /<email address hidden>
Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: #3 7ffca7536b70 b self-hosted:1013 (264b03e13e20 @ 492)
Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: #4 7ffca7536c60 b self-hosted:1013 (264b03e13e20 @ 492)
Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: #5 7ffca7536d70 b resource:
Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: #6 5615a5c69290 i /<email address hidden>
Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: #7 7ffca7537c80 b /<email address hidden>
Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: #8 5615a5c690d0 i /<email address hidden>
Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: #9 7ffca7538970 b self-hosted:1013 (264b03e13e20 @ 492)
Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: #10 5615a5c69018 i resource:
Versions:
$ lsb_release -rd
Description: Ubuntu 20.04.1 LTS
Release: 20.04
$ apt policy gnome-shell mutter gnome-shell-
gnome-shell:
Installed: 3.36.4-
Candidate: 3.36.4-
Version table:
*** 3.36.4-
500 http://
500 http://
100 /var/lib/
3.
500 http://
mutter:
Installed: 3.36.6-
Candidate: 3.36.6-
Version table:
*** 3.36.6-
500 http://
100 /var/lib/
3.
500 http://
gnome-shell-
Installed: 33.1-0ubuntu0.
Candidate: 33.1-0ubuntu0.
Version table:
*** 33.1-0ubuntu0.
500 http://
500 http://
100 /var/lib/
33-1 500
500 http://
500 http://
Status changed to 'Confirmed' because the bug affects multiple users.