Hide Forgot
Description of problem: When "Highlight Misspelled Words" is selected Gedit becomes very slow. In this case while highlight misspelled words was selected I carried out a text search. This caused the program to crash. Version-Release number of selected component: gedit-3.10.1-1.fc20 Additional info: reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: gedit grunhut.tex crash_function: _gtk_text_btree_get_chars_changed_stamp executable: /usr/bin/gedit kernel: 3.11.7-300.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 _gtk_text_btree_get_chars_changed_stamp at gtktextbtree.c:542 #1 gtk_text_iter_make_surreal at gtktextiter.c:172 #2 gtk_text_iter_compare at gtktextiter.c:5392 #3 redisplay_region at gtktextbtree.c:2620 #4 _gtk_text_btree_select_range at gtktextbtree.c:2905 #5 gtk_text_buffer_select_range at gtktextbuffer.c:2449 #6 start_search_finished at gedit-view-frame.c:334 #7 g_task_return_now at gtask.c:1108 #8 g_task_return at gtask.c:1161 #9 smart_forward_search_async_step at gtksourcesearchcontext.c:971 Potential duplicate: bug 709027
Created attachment 823429 [details] File: backtrace
Created attachment 823430 [details] File: cgroup
Created attachment 823431 [details] File: core_backtrace
Created attachment 823432 [details] File: dso_list
Created attachment 823433 [details] File: environ
Created attachment 823435 [details] File: exploitable
Created attachment 823436 [details] File: limits
Created attachment 823437 [details] File: maps
Created attachment 823439 [details] File: open_fds
Created attachment 823440 [details] File: proc_pid_status
Created attachment 823441 [details] File: var_log_messages
Another user experienced a similar problem: Searching for a text part in a text document. gedit crashed during search reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: gedit /home/kalle/Videos/eurolotto_20131225.txt crash_function: _gtk_text_btree_get_chars_changed_stamp executable: /usr/bin/gedit kernel: 3.12.5-302.fc20.x86_64 package: gedit-3.10.3-1.fc20 reason: gedit killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Just happened to same issue to me
Me, too. This is happening reliably when I search for text that occurs frequently in the document (e.g. Search for "e").
Another user experienced a similar problem: I opened a very large log file (385K lines) then closed gedit when I was finished reading it. reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: gedit /tmp/xa-IMyl9U/logcat.log crash_function: _gtk_text_btree_get_chars_changed_stamp executable: /usr/bin/gedit kernel: 3.15.9-200.fc20.x86_64 package: gedit-3.10.4-1.fc20 reason: gedit killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.