After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 785856 - Crashed on MPRIS
Crashed on MPRIS
Status: RESOLVED DUPLICATE of bug 785657
Product: gnome-shell
Classification: Core
Component: general
3.24.x
Other Linux
: Normal critical
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2017-08-05 13:16 UTC by Mike Manilone
Modified: 2017-08-16 17:48 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
stack trace (5.05 KB, text/plain)
2017-08-05 13:16 UTC, Mike Manilone
Details
full stacktrace (10.31 KB, text/plain)
2017-08-16 17:39 UTC, Mike Manilone
Details

Description Mike Manilone 2017-08-05 13:16:05 UTC
Created attachment 356998 [details]
stack trace

Netease Cloud Music [1] is an on-line music player from China. While in use, gnome-shell frequently crashes.

There are uncountable repeated JS errors reported in the logs:

    JS ERROR: Exception in callback for signal: changed: TypeError: 
     this._player.trackArtists.join is not a function
     MediaMessage<._update@resource:///org/gnome/shell/ui/mpris.js:92:23
     wrapper@resource:///org/gnome/gjs/modules/lang.js:178:22
     _emit@resource:///org/gnome/gjs/modules/signals.js:126:27
     MprisPlayer<._updateState@resource:///org/gnome/shell/ui/mpris.js:214:9
     wrapper@resource:///org/gnome/gjs/modules/lang.js:178:22

Environment: Arch Linux GNOME 3.24
Steps to Reproduce:
1. Listen to any song
2. Wait
3. GNOME-shell crashes

A stack trace from journalctl is attached. It seems that this crash is due to a race condition in GJS.

[1] https://music.163.com/#/download. I installed it via the archlinuxcn repo.
Comment 1 André Klapper 2017-08-16 00:11:08 UTC
Thanks for taking the time to report this.
Unfortunately, that stack trace is missing any elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash.
Can you get us a complete stack trace (in gdb, that would be "thread apply all bt full") with debugging symbols? 
See https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces for more information on how to do so and reopen this bug report. Thanks in advance!
Comment 2 Mike Manilone 2017-08-16 17:39:08 UTC
Created attachment 357745 [details]
full stacktrace

A full stack trace is attached.

Some symbols are still missing. Have no idea if they are optimized out.
Comment 3 Florian Müllner 2017-08-16 17:48:16 UTC
That's the same backtrace as the one in bug 785657. There's a gjs patch available on that bug that hopefully addresses this issue.

*** This bug has been marked as a duplicate of bug 785657 ***