abrt version: 1.1.13 architecture: x86_64 Attached file: backtrace cmdline: gedit /home/dobs/.cache/.fr-GeNgO7/sql_dump.23082010.sql component: gedit crash_function: _gtk_text_btree_get_chars_changed_stamp executable: /usr/bin/gedit kernel: 2.6.33.8-149.fc13.x86_64 package: gedit-1:2.30.2-1.fc13 rating: 4 reason: Process /usr/bin/gedit was killed by signal 11 (SIGSEGV) release: Fedora release 13 (Goddard) time: 1282862679 uid: 500 How to reproduce ----- 1. Open 65 Mb file... 2. 3.
Created an attachment (id=441352) File: backtrace
Package: gedit-1:2.30.2-1.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- opening mysqldump (~300K sql) crashes the gedit. If I rename it to .txt gedit opens it without a problem Comment ----- mysqldump > xxx.sql gedit xxx.sql
Package: gedit-1:2.30.2-1.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. I opened gedit using the command line. 2. I tried to open a 1.1MB file. 3. gedit crashed. Comment ----- I suspect the file was too big. It might have been nice to get a warning from gedit, rather than having it crash.
Package: gedit-1:2.30.2-1.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1.ouverture du fichier backup .sql d'une base de données avec gedit. 2. 3. Comment ----- Le fichier s'ouvre tres bien avec bluefish mais pas avec gedit. Il s'agit d'un fichier de backup de base mysql au format standard. Le fichier ne fait que 350ko
Package: gedit-1:2.30.2-1.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Start with gedit <file> 2. <File> contains a MySql dump, with an extremely long line (295798 chars)
Package: gedit-1:2.30.2-1.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Opened a large (3.1Mb) text file in gedit.
(In reply to comment #6) > How to reproduce > ----- > 1. Opened a large (3.1Mb) text file in gedit. As with other commentors on this bug, the file in question was a MySQL dump file with very long lines.
Package: gedit-1:2.30.2-1.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. gedit <document.html> & 2. type text in document 3. hit <backspace> Comment ----- The document contains XHTML During startup the console showed: GtkSourceView-CRITICAL **: Highlighting a single line took too much time, syntax highlighting will be disabled At the moment of the crash: Gtk-CRITICAL **: gtk_text_buffer_get_iter_at_offset: assertion `GTK_IS_TEXT_BUFFER (buffer)' failed Gtk-CRITICAL **: gtk_text_buffer_move_mark: assertion `GTK_IS_TEXT_MARK (mark)' failed
*** Bug 595410 has been marked as a duplicate of this bug. ***
*** Bug 608159 has been marked as a duplicate of this bug. ***
*** Bug 618851 has been marked as a duplicate of this bug. ***
*** Bug 622031 has been marked as a duplicate of this bug. ***
*** Bug 624172 has been marked as a duplicate of this bug. ***
Package: gedit-1:2.30.2-1.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- gedit crashes in various ways but not necessarily for a clear reason
Package: gedit-1:2.30.2-1.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Download a large html file and Remove all newlines (or just uncompress attachment I provide) 2. open in gedit 3. move cursor to front of file 4. press space 5. press backspace 6. wait a few seconds and gedit will crash it works 100% of the time for me.
Created attachment 459692 [details] This is an example of a large html file without newlines. Open in gedit, place cursor at top of file, press space, press backspace.
I previously reported this as https://bugzilla.redhat.com/show_bug.cgi?id=559446
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. 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 WONTFIX if it remains open with a Fedora 'version' of '13'. 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 prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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. Thank you for reporting this bug and we are sorry it could not be fixed.