Terminal/VTE hanging problem

[Bernhard Walle]

* Benedikt Meurer [17.08.2005 20:02]:
> Bernhard Walle wrote:
>> I also got a report via PM that he has the same problem. (gentoo amd64
>> with xfce 4.2.2)
> 
> I have no real idea what could cause the increased CPU usage yet. Which
> process causes the load? Terminal or Xorg?

Terminal.

I tried to step down the problem a bit (unfortunately, my Gtk knowledge
with events is very small).

A backtrace:




#0  0x409489d8 in re_search_internal () from /lib/tls/libc.so.6
#1  0x40948ffb in regexec@@GLIBC_2.3.4 () from /lib/tls/libc.so.6
#2  0x40156867 in _vte_regex_exec (regex=0x8262300, string=0x8262300
"�#\bH", nmatch=256, matches=0xbfffdb80)
    at vteregex.c:252
#3  0x40145554 in vte_terminal_match_check_internal (terminal=0x8122cd8,
column=20, row=55, tag=0x0, start=0xbfffe3c8,
    end=0xbfffe3cc) at vte.c:1647
#4  0x40145a92 in vte_terminal_match_hilite (terminal=0x8122cd8,
x=55.857142857142854, y=222) at mathinline.h:530
#5  0x401480ce in vte_terminal_motion_notify (widget=0x8122cd8,
event=0x8207998) at vte.c:10287
#6  0x4046881e in _gtk_marshal_BOOLEAN__BOXED (closure=0x80e1530,
return_value=0xbfffe5b0, n_param_values=2,
    param_values=0xbfffe700, invocation_hint=0xbfffe5d8,
marshal_data=0x40147fa0) at gtkmarshalers.c:83
#7  0x407f7279 in g_type_class_meta_marshal (closure=0x80e1530,
return_value=0x8262300, n_param_values=136717056,
    param_values=0xbfffe700, invocation_hint=0x8262300,
marshal_data=0x8262300) at gclosure.c:514
#8  0x407f78db in IA__g_closure_invoke (closure=0x80e1530,
return_value=0x8262300, n_param_values=136717056,
    param_values=0x8262300, invocation_hint=0x8262300) at gclosure.c:437
#9  0x40807179 in signal_emit_unlocked_R (node=0x80e0868, detail=0,
instance=0x8122cd8, emission_return=0xbfffe690,
    instance_and_params=0xbfffe700) at gsignal.c:2523
#10 0x40807ff2 in IA__g_signal_emit_valist (instance=0x8122cd8,
signal_id=30, detail=0,
    var_args=0xbfffe890 "���\230y \b���\217AU@\003") at gsignal.c:2254
#11 0x40808626 in IA__g_signal_emit (instance=0x8262300,
signal_id=136717056, detail=136717056) at gsignal.c:2288
#12 0x4054ff14 in gtk_widget_event_internal (widget=0x8122cd8,
event=0x8207998) at gtkwidget.c:3631
#13 0x404622f9 in IA__gtk_propagate_event (widget=0x8122cd8,
event=0x8207998) at gtkmain.c:2146
#14 0x4046374f in IA__gtk_main_do_event (event=0x8207998) at gtkmain.c:1384
#15 0x40716ed2 in gdk_event_dispatch (source=0x8262300, callback=0,
user_data=0x0) at gdkevents-x11.c:2221
#16 0x4084f967 in IA__g_main_context_dispatch (context=0x80c2e38) at
gmain.c:1947
#17 0x40851ce2 in g_main_context_iterate (context=0x80c2e38, block=1,
dispatch=1, self=0x80d5208) at gmain.c:2578
#18 0x40852cf7 in IA__g_main_loop_run (loop=0x80a1880) at gmain.c:2782
#19 0x40463be3 in IA__gtk_main () at gtkmain.c:963
#20 0x0805418d in main (argc=1, argv=0xbfffeb74) at main.c:271

The problem happens while responding to G_MOTION events (#12,
event->type == GDK_MOTION_NOTIFY).

And in fact, if I move the mouse outside the Terminal window (before
doing the experiment) and scroll using the keyboard, there's no problem.


Regards,
  Bernhard