GNOME Bugzilla – Bug 709229
GNOME Documents crashes with segmentation fault when editing Google Docs
Last modified: 2014-04-27 16:07:02 UTC
GNOME Documents always crashes with a segmentation fault when editing Google Docs with it. Here's the terminal output: Gjs-Message: JS LOG: Can't find a valid getting started PDF document java version "1.7.0_40" OpenJDK Runtime Environment (IcedTea 2.4.1) (suse-23.1-x86_64) OpenJDK 64-Bit Server VM (build 24.0-b50, mixed mode) (gnome-documents:9547): GLib-GIO-CRITICAL **: g_file_new_for_uri: assertion 'uri != NULL' failed (gnome-documents:9547): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed ** Message: console message: https://docs.google.com/document/d/1lTFBfM5OQBszeEQ7r6SJ8xZW440hxlhhMhnyiXLrKk4/edit?usp=docslist_api&pli=1 @1: Viewport argument key "minimum-scale:1.0" not recognized and ignored. ** Message: console message: https://docs.google.com/document/d/1lTFBfM5OQBszeEQ7r6SJ8xZW440hxlhhMhnyiXLrKk4/edit?usp=docslist_api&pli=1 @1: Viewport argument key "maximum-scale:1.0" not recognized and ignored. Segmentation fault
(In reply to comment #0) > (gnome-documents:9547): GLib-GIO-CRITICAL **: g_file_new_for_uri: assertion > 'uri != NULL' failed > > (gnome-documents:9547): GLib-GObject-CRITICAL **: g_object_unref: assertion > 'G_IS_OBJECT (object)' failed That is due to bug 715032 > ** Message: console message: > https://docs.google.com/document/d/1lTFBfM5OQBszeEQ7r6SJ8xZW440hxlhhMhnyiXLrKk4/edit?usp=docslist_api&pli=1 > @1: Viewport argument key "minimum-scale:1.0" not recognized and ignored. > > ** Message: console message: > https://docs.google.com/document/d/1lTFBfM5OQBszeEQ7r6SJ8xZW440hxlhhMhnyiXLrKk4/edit?usp=docslist_api&pli=1 > @1: Viewport argument key "maximum-scale:1.0" not recognized and ignored. > > Segmentation fault Can I have a backtrace of the crash?
Also, what is your version of webkitgtk? I got webkitgtk3-2.2.2-1.fc20
Hello I'm using libwebkitgtk3-2.2.2-8.3. Unfortunately, I'm unable to backtrace the crash through gdb. I'm getting this error when I attempt to run the application: "Starting program: No executable file specified. Use the "file" or "exec-file" command". What should I do to get gnome-documents debugged via gdb?
(In reply to comment #3) > What should I do to get gnome-documents debugged via gdb? One option is to start gnome-documents as usual, and then attach gdb to it and continue: $ gdb /path/to/gnome-documents <PID of gjs running gnome-documents> (gdb) continue ...
Here's the output, I hope it helps: https://dl.dropboxusercontent.com/u/44544435/gdb%20gnome-documents.txt
(In reply to comment #5) > Here's the output, I hope it helps: > https://dl.dropboxusercontent.com/u/44544435/gdb%20gnome-documents.txt Thank you very much. So it crashes from inside webkitgtk. It would have been better if you had some of the debuginfo packages installed so that the backtrace would have had more information. Also, you should replace /path/to/gnome-documents with the output of "which gnome-documents". :-) Otherwise if you can share a document with me (debarshi.ray@gmail.com) which triggers this crash, I can do the digging for you. Thanks for your help with this bug so far.
I already had gnome-documents-debuginfo installed. Would you like me to repeat the proccess with libwebkitgtk3-debuginfo installed? I have already sent you an email with the link to the Drive document that I have been attempting to edit. Thank you for your hard work
Thank you for sharing the document. Do I have to do anything particular to trigger the crash? Or does it crash if I open the document and click "Edit" from the gear menu? I only have an older Fedora 19 (running GNOME 3.8) system now and I am unable to reproduce the crash on it. Maybe it only crashes on GNOME 3.10?
Just clicking on edit from the gear menu are enough to crash it. It loads the page, freezes for 2 minutes, then crashes. I don't remember having this problem on 3.8 so it's likely that the issue only occurs on 3.10
Created attachment 261432 [details] Crash reproducer Could be a regression in webkitgtk.
Reported as a WebKit bug: https://bugs.webkit.org/show_bug.cgi?id=124949