GNOME Bugzilla – Bug 611069
Using invisible chars causes a Gtk-ERROR: Byte index is off the end of the line
Last modified: 2018-04-15 00:08:32 UTC
Created attachment 154681 [details] Short Python file needed to reproduce the bug Hello, This report follows https://bugs.launchpad.net/dreampie/+bug/525429 ; I've managed to reproduce it without the need of a big GUI application. To reproduce: Download the attached fold_bug.py file. Run: python fold_bug.py. A window appears, blank because it didn't have the time to refresh. Move the mouse cursor over the window. I get this: fold_bug.py:19: GtkWarning: /build/buildd/gtk+2.0-2.18.3/gtk/gtktextbtree.c:4017: byte index off the end of the line gtk.main_iteration(False) Gtk-ERROR **: Byte index 12 is off the end of the line aborting... Aborted (core dumped) I attach the relevant lines from the stack trace created by gdb. I'm using ubuntu karmic 9.10 on i386. Thanks, Noam
Created attachment 154682 [details] Traceback created by gdb
Created attachment 206794 [details] Another python program which shows the bug, using GI I changed the Python program a bit, to use GI and to be a bit clearer. It now adds the lines when idle, so the window is drawn.
Created attachment 206795 [details] [review] A patch which fixes the bug! (copied from the patch: ) GtkTextView uses does some processing when idle. However, if events are handled before the processing is done, the program may crash. This change makes sure that the processing is done before events are handled.
Please fix it, we have patch, you just need to review it and implement it.. How long it usually takes them ( developer ) to fix bug ?
We're moving to gitlab! As part of this move, we are moving bugs to NEEDINFO if they haven't seen activity in more than a year. If this issue is still important to you and still relevant with GTK+ 3.22 or master, please reopen it and we will migrate it to gitlab.
As announced a while ago, we are migrating to gitlab, and bugs that haven't seen activity in the last year or so will be not be migrated, but closed out in bugzilla. If this bug is still relevant to you, you can open a new issue describing the symptoms and how to reproduce it with gtk 3.22.x or master in gitlab: https://gitlab.gnome.org/GNOME/gtk/issues/new