GNOME Bugzilla – Bug 536051
gedit memory hungry + crash on extremely long lines
Last modified: 2008-11-29 11:26:10 UTC
Please describe the problem: When reading very large lines, gedit dies. Older computers may need to force a x kill to get out of it. Steps to reproduce: 1. Create a big file on a single line, or add an extremely long line to an existing file (mine was over 1.50MiB) 2. Open the file, go to the long line 3. Watch gedit die slowly and painfully Actual results: Freeze, crash eventually. Loss of any unsaved data, etc. Better setups will read the file, but the line will be garbled (and not split) Expected results: Proper memory handling. Does this happen every time? Yes. Also happens with and without line numbers on. Didn't test without text wrapping. Other information:
I reported this issue at https://bugs.launchpad.net/bugs/256557 . I can confirm it with gedit 2.23.1. It's very reproducible, and happens with and without text wrapping.
I guess that is a bug in gtksourceview. In gtksourceview.c: /** * gtk_source_view_set_show_line_marks: * @view: a #GtkSourceView. * @show: whether line marks should be displayed. * * If %TRUE line marks will be displayed beside the text. * * Since: 2.2 **/ I think that gedit should not read the whole line at once. It should show just a part of the line and display it into screen.
This is a known issue in GtkTextView... little we can do. I am closing this as INVALID even if it's not really invalid... it's more of a duplicate of the gtk report, but I can't find it right now.