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 675593 - Anjuta sometimes locks up on command completion
Anjuta sometimes locks up on command completion
Status: RESOLVED OBSOLETE
Product: anjuta
Classification: Applications
Component: plugins: language-support-c-cpp-java
3.5.x
Other Linux
: Normal normal
: ---
Assigned To: Naba Kumar
Anjuta maintainers
Depends on:
Blocks:
 
 
Reported: 2012-05-07 09:14 UTC by Jens Georg
Modified: 2020-11-06 20:22 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Jens Georg 2012-05-07 09:14:14 UTC
During editing anjuta randomly locks up while trying to complete system symbols (I think). It's kind of reproducible; it happens sometime in an editing session but unfortunately it's rather random. Symptoms are that the symbol window stays popped up and anjuta is unresponsive.

Backtrace:

Thread 1 (Thread 0x7f1242089940 (LWP 5626))

  • #0 escape_string
    at gmessages.c line 1085
  • #1 g_log_default_handler
    at gmessages.c line 1238
  • #2 g_logv
    at gmessages.c line 733
  • #3 g_log
    at gmessages.c line 792
  • #4 g_type_check_instance_cast
    at gtype.c line 4011
  • #5 update_completion
    at gtksourcecompletion.c line 3169
  • #6 update_interactive_completion
    at gtksourcecompletion.c line 1653
  • #7 buffer_delete_range_cb
    at gtksourcecompletion.c line 1691
  • #8 g_closure_invoke
    at gclosure.c line 777
  • #9 signal_emit_unlocked_R
    at gsignal.c line 3617
  • #10 g_signal_emit_valist
    at gsignal.c line 3296
  • #11 g_signal_emit
    at gsignal.c line 3352
  • #12 gtk_text_buffer_delete_interactive
    at gtktextbuffer.c line 1760
  • #13 gtk_text_buffer_backspace
    at gtktextbuffer.c line 3929
  • #14 gtk_text_view_backspace
    at gtktextview.c line 5966
  • #15 g_closure_invoke
    at gclosure.c line 777
  • #16 signal_emit_unlocked_R
    at gsignal.c line 3585
  • #17 g_signal_emitv
    at gsignal.c line 3037
  • #18 gtk_binding_entry_activate
    at gtkbindings.c line 651
  • #19 binding_activate
    at gtkbindings.c line 1523
  • #20 gtk_bindings_activate_list
    at gtkbindings.c line 1584
  • #21 gtk_bindings_activate_event
    at gtkbindings.c line 1669
  • #22 gtk_text_view_key_press_event
    at gtktextview.c line 4444
  • #23 gtk_source_view_key_press_event
    at gtksourceview.c line 3478
  • #24 _gtk_marshal_BOOLEAN__BOXED
    at gtkmarshalers.c line 85
  • #25 g_closure_invoke
    at gclosure.c line 777
  • #26 signal_emit_unlocked_R
    at gsignal.c line 3585
  • #27 g_signal_emit_valist
    at gsignal.c line 3306
  • #28 g_signal_emit
    at gsignal.c line 3352
  • #29 gtk_widget_event_internal
    at gtkwidget.c line 6380
  • #30 gtk_window_propagate_key_event
    at gtkwindow.c line 6046
  • #31 anjuta_app_key_press_event
    at anjuta-app.c line 751
  • #32 _gtk_marshal_BOOLEAN__BOXED
    at gtkmarshalers.c line 85
  • #33 g_closure_invoke
    at gclosure.c line 777
  • #34 signal_emit_unlocked_R
    at gsignal.c line 3585
  • #35 g_signal_emit_valist
    at gsignal.c line 3306
  • #36 g_signal_emit
    at gsignal.c line 3352
  • #37 gtk_widget_event_internal
    at gtkwidget.c line 6380
  • #38 propagate_event
    at gtkmain.c line 2479
  • #39 gtk_main_do_event
    at gtkmain.c line 1713
  • #40 gdk_event_source_dispatch
    at gdkeventsource.c line 358
  • #41 g_main_dispatch
    at gmain.c line 2539
  • #42 g_main_context_dispatch
    at gmain.c line 3075
  • #43 g_main_context_iterate
    at gmain.c line 3146
  • #44 g_main_context_iterate
    at gmain.c line 3083
  • #45 g_main_context_iteration
    at gmain.c line 3207
  • #46 g_application_run
    at gapplication.c line 1496
  • #47 main
    at main.c line 211

Comment 1 Johannes Schmid 2012-05-07 09:58:06 UTC
Thanks for the trace. This is probably a dup bug #663241. I fear this is a multi-threading issues so it's really hard to find but I will try to have a second look.
Comment 2 Jens Georg 2012-05-07 10:10:30 UTC
yes, that looks quite similar
Comment 3 Sébastien Wilmet 2013-02-20 20:53:29 UTC
Can you still reproduce this bug with the master git branch of GtkSourceView? (or the latest development release)

Because some bugs have been fixed in the completion system of GtkSourceView recently.
Comment 4 André Klapper 2020-11-06 20:22:48 UTC
bugzilla.gnome.org is being replaced by gitlab.gnome.org. We are closing all old bug reports in Bugzilla which have not seen updates for many years.

If you can still reproduce this issue in a currently supported version of GNOME (currently that would be 3.38), then please feel free to report it at https://gitlab.gnome.org/GNOME/anjuta/-/issues/

Thank you for reporting this issue and we are sorry it could not be fixed.