Created attachment 1232538 [details] Displayerror with gedit Please enable the security flag for this report! Description of problem: When i open a 80 MB ascii-text logfile, the contentframe is going black. if i select a line, i can see that one normaly, the rest stays black. Selecting the text with CTRL+A => gets white on blue, as it should be. Scrolling doesn't help unfocusing the window, makes the content appear, as greyed out as you can see on the screenhot. As soon as you focus the gedit window again, it's black on black again. My fears => Buffer Overrun in the syntax highlighing engine. IF that is true, this could be tricked by a ZIP Bomb containing MB of <SPACE> or any other good compressable contant and will be sent via email. Notes: "Reiner Text" means "pure ascii text" as syntax-highlight selection. Chaning it, does not help in any way. Version-Release number of selected component (if applicable): gedit-plugin-charmap-3.20.0-1.fc24.x86_64 gedit-plugin-drawspaces-3.20.0-1.fc24.x86_64 gedit-plugin-codecomment-3.20.0-1.fc24.x86_64 gedit-plugin-commander-3.20.0-1.fc24.x86_64 gedit-plugin-multiedit-3.20.0-1.fc24.x86_64 gedit-cossa-3.2.0-10.fc24.x86_64 gedit-plugins-data-3.20.0-1.fc24.x86_64 gedit-plugin-zeitgeist-3.20.0-1.fc24.x86_64 gedit-plugin-colorschemer-3.20.0-1.fc24.x86_64 gedit-plugin-joinlines-3.20.0-1.fc24.x86_64 gedit-plugin-synctex-3.20.0-1.fc24.x86_64 gedit-plugin-bracketcompletion-3.20.0-1.fc24.x86_64 gedit-plugin-dashboard-3.20.0-1.fc24.x86_64 gedit-plugin-smartspaces-3.20.0-1.fc24.x86_64 gedit-plugin-bookmarks-3.20.0-1.fc24.x86_64 gedit-plugins-3.20.0-1.fc24.x86_64 gedit-plugin-findinfiles-3.20.0-1.fc24.x86_64 gedit-plugin-terminal-3.20.0-1.fc24.x86_64 gedit-3.20.2-1.fc24.x86_64 gedit-plugin-wordcompletion-3.20.0-1.fc24.x86_64 gedit-plugin-colorpicker-3.20.0-1.fc24.x86_64 gedit-plugin-git-3.20.0-1.fc24.x86_64 gedit-plugin-textsize-3.20.0-1.fc24.x86_64 How reproducible: Steps to Reproduce: 1. Take a text logile of 80MB 2. open it Actual results: the content is black if the window is focused Expected results: normal color theme
The error is only in this open tag, the other you see on the screenshot is unharmed.
I did this: base64 /dev/urandom | head -c 800000000 > file.txt gedit file.txt No problems. Perhaps there is an issue with the data in your file, or possibly a problem with your color scheme ?
as no highlighting was enabled, i would map that one out, but maybe a ISO-8859-1 char inside the file on a UTF-8 system ????
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 '24'. 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 24 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 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.