GNOME Bugzilla – Bug 779874
warning on exit that can lead to a crash.
Last modified: 2017-06-25 19:57:14 UTC
Gnome maps is printing this on exit: Gjs-Message: JS WARNING: [resource:///org/gnome/Maps/js/placeStore.js 309]: reference to undefined property this._typeTable[place.uniqueID] (gnome-maps:17403): Gjs-CRITICAL **: 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() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. (gnome-maps:17403): Gjs-CRITICAL **: The offending signal was destroy on Gjs_UserLocationMarker 0x401ee00. I asked ptomato on irc. He said: "you shouldn't connect to the 'destroy' signal in GJS and it looks like UserLocationMarker does so"
Created attachment 347775 [details] [review] userLocationMarker: Don't connect to destroy Instead of connecting to the destoy signal to disconnect from the MapView zoom-level property, explicitly disconnect the signal handler when re-creating the marker in the MapView.
I haven't been able to reproduce the actual bug, but the above patch should at least theoretically solve this problem. Also I haven't really been able to excersize this patch, as my development machine is a desktop machine and has no WiFi h/w, and thus by its nature keeps a static location. But it should probably work (but ofcourse testing would be appreciated).
Same here. No wifi hardware. Just a desktop connected to a neighborhood cable provider through an ethernet cable. Pressing 'go to current location' always showed the pin at the address of the cable provider instead of mine. The patch does however stop the warning. Thank you very much!
Attachment 347775 [details] pushed as b763a33 - userLocationMarker: Don't connect to destroy