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 736650 - crash when saving file
crash when saving file
Status: RESOLVED DUPLICATE of bug 738981
Product: gedit-plugins
Classification: Other
Component: General
3.14.x
Other Linux
: Normal critical
: ---
Assigned To: Gedit maintainers
Gedit maintainers
Depends on:
Blocks:
 
 
Reported: 2014-09-14 20:09 UTC by Igor Gnatenko
Modified: 2019-03-23 20:54 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
backtrace (20.57 KB, text/plain)
2014-10-17 08:58 UTC, Igor Gnatenko
Details
valgrind log (287.21 KB, application/gzip)
2014-10-17 09:06 UTC, Igor Gnatenko
Details

Description Igor Gnatenko 2014-09-14 20:09:09 UTC


Thread 6 (Thread 0x7fffd69e0700 (LWP 15841))

  • #0 __strchr_sse2
    at ../sysdeps/x86_64/strchr.S line 24
  • #1 g_strdelimit
    at gstrfuncs.c line 1946
  • #2 g_signal_newv
  • #3 g_signal_new_valist
    at gsignal.c line 1840
  • #4 g_signal_new
    at gsignal.c line 1395
  • #5 gvfs_metadata_default_init
  • #6 type_iface_ensure_dflt_vtable_Wm
    at gtype.c line 1958
  • #7 type_iface_vtable_base_init_Wm
    at gtype.c line 1987
  • #8 g_type_class_ref
    at gtype.c line 2178
  • #9 g_type_class_ref
    at gtype.c line 2932
  • #10 g_object_new_valist
    at gobject.c line 1960
  • #11 g_initable_new_valist
    at ginitable.c line 224
  • #12 g_initable_new
    at ginitable.c line 146
  • #13 gvfs_metadata_proxy_new_for_bus_sync
  • #14 _g_daemon_vfs_get_metadata_proxy
  • #15 g_daemon_vfs_local_file_set_attributes
  • #16 _g_local_file_info_set_attributes
    at glocalfileinfo.c line 2652
  • #17 g_local_file_set_attributes_from_info
    at glocalfile.c line 1321
  • #18 set_info_async_thread
    at gfile.c line 6054
  • #19 g_task_thread_pool_thread
    at gtask.c line 1215
  • #20 g_thread_pool_thread_proxy
    at gthreadpool.c line 307
  • #21 g_thread_proxy
    at gthread.c line 764
  • #22 start_thread
    at pthread_create.c line 310
  • #23 clone
    at ../sysdeps/unix/sysv/linux/x86_64/clone.S line 109

Thread 1 (Thread 0x7ffff7fba980 (LWP 15833))

  • #0 g_type_check_instance
    at gtype.c line 4085
  • #1 g_signal_emit_by_name
    at gsignal.c line 3391
  • #5 <emit signal 0x7fffdd1da1a9 "changed" on instance 0x7fffe000c150 [GeditDocument]>
    at gsignal.c line 3405
  • #6 save_cb
    at gedit/gedit-tab.c line 2277
  • #7 g_task_return_now
    at gtask.c line 1077
  • #8 g_task_return
    at gtask.c line 1130
  • #9 query_info_cb
    at gtksourcefilesaver.c line 547
  • #10 g_task_return_now
    at gtask.c line 1077
  • #11 complete_in_idle_cb
    at gtask.c line 1086
  • #12 g_main_context_dispatch
    at gmain.c line 3064
  • #13 g_main_context_dispatch
    at gmain.c line 3663
  • #14 g_main_context_iterate
    at gmain.c line 3734
  • #15 g_main_context_iteration
    at gmain.c line 3795
  • #16 g_application_run
    at gapplication.c line 2282
  • #17 main
    at gedit/gedit.c line 133

3.13.91
Comment 1 Sébastien Wilmet 2014-09-15 22:01:21 UTC
Where does it crash? In g_type_check_instance() for the thread with the main?

The GObject gdb plugin seems to be buggy, because it's the "saved" signal that is sent, not "changed". And the "saved" signal had an error parameter before, that has been removed. So the problem comes maybe from a plugin which was not updated.
Comment 2 Sébastien Wilmet 2014-09-18 13:17:40 UTC
Do you still have the core? What does gdb print? In which thread does it crash?

Normally all official gedit plugins should work fine, including those in gedit-plugins.
Comment 3 Igor Gnatenko 2014-10-17 08:54:20 UTC
yes.

https://bugzilla.redhat.com/show_bug.cgi?id=1144758

with synctex it's crashing
Comment 4 Igor Gnatenko 2014-10-17 08:56:25 UTC
hm. I've disabled synctex and it's crashing
Comment 5 Igor Gnatenko 2014-10-17 08:58:44 UTC
Created attachment 288730 [details]
backtrace

I can reproduce on 3.14.0
Comment 6 Igor Gnatenko 2014-10-17 09:06:44 UTC
Created attachment 288731 [details]
valgrind log

G_SLICE=always-malloc G_DEBUG=gc-friendly  valgrind -v --tool=memcheck --leak-check=full --num-callers=40 --log-file=valgrind.log gedit Linux\ today\ and\ tomorrow.tex

and saved it
Comment 7 Ignacio Casal Quinteiro (nacho) 2014-10-17 09:09:34 UTC
I guess this is the reason:
==1354== 1 errors in context 1 of 4175:
==1354== Invalid read of size 8
==1354==    at 0x7F3B40D: g_type_check_instance (gtype.c:4085)
==1354==    by 0x7F3247B: g_signal_emit_by_name (gsignal.c:3391)
==1354==    by 0x7F17D34: g_closure_invoke (gclosure.c:768)
==1354==    by 0x7F29A51: signal_emit_unlocked_R (gsignal.c:3553)
==1354==    by 0x7F32190: g_signal_emit_valist (gsignal.c:3309)
==1354==    by 0x7F32909: g_signal_emit_by_name (gsignal.c:3405)
==1354==    by 0x4E84434: save_cb (gedit-tab.c:2277)
==1354==    by 0x79E03DA: g_task_return_now (gtask.c:1077)
==1354==    by 0x79E0A65: g_task_return (gtask.c:1130)
==1354==    by 0x54836A9: query_info_cb (gtksourcefilesaver.c:550)
==1354==    by 0x79E03DA: g_task_return_now (gtask.c:1077)
==1354==    by 0x79E03F8: complete_in_idle_cb (gtask.c:1086)
==1354==    by 0x81A2AFA: g_main_dispatch (gmain.c:3111)
==1354==    by 0x81A2AFA: g_main_context_dispatch (gmain.c:3710)
==1354==    by 0x81A2E97: g_main_context_iterate.isra.29 (gmain.c:3781)
==1354==    by 0x81A2F4B: g_main_context_iteration (gmain.c:3842)
==1354==    by 0x7A0307B: g_application_run (gapplication.c:2282)
==1354==    by 0x400DF9: main (gedit.c:135)
==1354==  Address 0x1 is not stack'd, malloc'd or (recently) free'd
Comment 8 Sébastien Wilmet 2014-10-18 10:14:41 UTC
Is it 100% reproducible? Does it also happen with all plugins disabled?

It's maybe a plugin not updated wrt the GeditDocument::saved signal.
Comment 9 Igor Gnatenko 2014-10-22 09:17:17 UTC
yes. this is 100% reproducible. problem in gedit-code-assistance plugin.
Comment 10 Sébastien Wilmet 2014-10-22 09:23:06 UTC
gedit-code-assistance needs a new release, I think the problem is fixed in git master.
Comment 11 Sébastien Wilmet 2014-12-18 10:30:07 UTC

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