Description of problem: I opened a randomly generated plain text file (ASCII only) with single about 500k characters long line. Mousepad crashed immediately. OTOH, I have seen it open similar file with longer line and not crash) Version-Release number of selected component: mousepad-0.3.0-3.fc20 Additional info: reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: mousepad /home/me/tmp/testfile-524288.txt crash_function: mousepad_file_open executable: /usr/bin/mousepad kernel: 3.11.10-301.fc20.x86_64 runlevel: N 5 type: CCpp uid: 22482 Truncated backtrace: Thread no. 1 (4 frames) #0 mousepad_file_open at mousepad-file.c:545 #1 mousepad_window_open_file at mousepad-window.c:1012 #2 mousepad_window_open_files at mousepad-window.c:1148 #3 mousepad_application_new_window_with_files at mousepad-application.c:285
Created attachment 847772 [details] File: backtrace
Created attachment 847773 [details] File: cgroup
Created attachment 847774 [details] File: core_backtrace
Created attachment 847775 [details] File: dso_list
Created attachment 847776 [details] File: environ
Created attachment 847777 [details] File: exploitable
Created attachment 847778 [details] File: limits
Created attachment 847779 [details] File: maps
Created attachment 847780 [details] File: open_fds
Created attachment 847781 [details] File: proc_pid_status
Created attachment 847782 [details] File: var_log_messages
Created attachment 847783 [details] File: mousepad-crashfile.txt.gz
I have performed couple of additional tests and found out that mousepad seems to crash if the file * contains N characters long line (tested with single line, ASCII (in fact [a-zA-Z], no whitespace at all); * N = 2 ** I; where I > 16 So with line that is 2**16 long, mousepad works OK, but wit 2**17 it crashes, and so with 2**18 etc. I have also confirmed with the original file (line 2**19 long): * with N - 1, OK, * with N, crash, and * with N + 1, OK again. Note that this was found by accident when playing with recently reported bug 1051083, so the syndromes reported there were in place.
So, I can try and take a look, but mousepad is pretty much unmaintained upstream anymore and probibly should just be dropped. Can you duplicate the problem in leafpad?
> ...dropped. What?! My favorite editor? ;-) > Can you duplicate the problem in leafpad? I tested with "I" from 16 to 20 in leafpad and the crash did not happen. So the problem is apparently leafpad-specific.
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.