GNOME Bugzilla – Bug 688594
gnome-documents crashes if you go back from fullscreen and scroll
Last modified: 2013-01-03 02:24:36 UTC
Backtrace:
+ Trace 231187
Additionally, I'm seeing criticals related to GdSidebarThumbnails while in fullscreen. JS backtrace: == Stack trace for context 0x610cf0 == 0 anonymous("model" = [object GObject_Object])@/opt/gnome/share/gnome-documents/js/preview.js:205 1 wrapper([object GObject_Object])@/opt/gnome/share/gjs-1.0/lang.js:204 2 anonymous([object GObject_Object])@/opt/gnome/share/gjs-1.0/lang.js:145 3 anonymous([object GObject_Object])@/opt/gnome/share/gjs-1.0/lang.js:239 4 anonymous("parentActor" = [object GObject_Object], "layout" = [object GObject_Object], "previewView" = [object Object])@/opt/gnome/share/gnome-documents/js/preview.js:247 5 wrapper([object Object], [object GObject_Object], [object GObject_Object])@/opt/gnome/share/gjs-1.0/lang.js:204 6 anonymous([object Object], [object GObject_Object], [object GObject_Object])@/opt/gnome/share/gjs-1.0/lang.js:145 7 anonymous([object Object], [object GObject_Object], [object GObject_Object])@/opt/gnome/share/gjs-1.0/lang.js:239 8 anonymous("fullscreen" = true, "controller" = [object Object])@/opt/gnome/share/gnome-documents/js/embed.js:460 9 wrapper([object Object], true)@/opt/gnome/share/gjs-1.0/lang.js:204 10 _emit("name" = ""fullscreen-changed"", true)@/opt/gnome/share/gjs-1.0/signals.js:124 11 anonymous("fullscreen" = true)@/opt/gnome/share/gnome-documents/js/windowMode.js:77 12 wrapper(true)@/opt/gnome/share/gjs-1.0/lang.js:204 13 anonymous()@/opt/gnome/share/gnome-documents/js/windowMode.js:81 14 wrapper()@/opt/gnome/share/gjs-1.0/lang.js:204 15 anonymous("event" = [object GObject_Union], "widget" = [object GObject_Object])@/opt/gnome/share/gnome-documents/js/preview.js:140 16 wrapper([object GObject_Object], [object GObject_Union])@/opt/gnome/share/gjs-1.0/lang.js:204 17 start()@/opt/gnome/share/gnome-documents/js/main.js:33 18 <TOP LEVEL>@<command line>:1 Full stack trace:
+ Trace 231188
Working around bug 688596 fixed the criticals, and hopefully the crash too.
No, the crash is still there. Might be caused by a signal which is not disconnected.
How do I reproduce it exactly? I don't see it here.
(In reply to comment #4) > How do I reproduce it exactly? I don't see it here. I'm not sure, actually. I just went back and forth from fullscreen a few times, scrolled the document, and bam, app is gone. I have a local patch that fixes the lifetime of signals, but it still has dangerous criticals if you go back from fullscreen.
Bah, let's assume it is fixed in master, and restart debugging if it happens again.