Bug 1051166

Summary: [abrt] mousepad-0.3.0-3.fc20: mousepad_file_open: Process /usr/bin/mousepad was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Alois Mahdal <amahdal>
Component: mousepadAssignee: Kevin Fenzi <kevin>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: kevin
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/178acf342011689212f3fa902f33510643d8854a
Whiteboard: abrt_hash:76d3da37225e80dd1b2198af422002c4ef97d53c
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-30 00:50:32 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages
none
File: mousepad-crashfile.txt.gz none

Description Alois Mahdal 2014-01-09 19:24:35 UTC
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

Comment 1 Alois Mahdal 2014-01-09 19:24:40 UTC
Created attachment 847772 [details]
File: backtrace

Comment 2 Alois Mahdal 2014-01-09 19:24:42 UTC
Created attachment 847773 [details]
File: cgroup

Comment 3 Alois Mahdal 2014-01-09 19:24:45 UTC
Created attachment 847774 [details]
File: core_backtrace

Comment 4 Alois Mahdal 2014-01-09 19:24:47 UTC
Created attachment 847775 [details]
File: dso_list

Comment 5 Alois Mahdal 2014-01-09 19:24:49 UTC
Created attachment 847776 [details]
File: environ

Comment 6 Alois Mahdal 2014-01-09 19:24:51 UTC
Created attachment 847777 [details]
File: exploitable

Comment 7 Alois Mahdal 2014-01-09 19:24:53 UTC
Created attachment 847778 [details]
File: limits

Comment 8 Alois Mahdal 2014-01-09 19:24:55 UTC
Created attachment 847779 [details]
File: maps

Comment 9 Alois Mahdal 2014-01-09 19:24:57 UTC
Created attachment 847780 [details]
File: open_fds

Comment 10 Alois Mahdal 2014-01-09 19:24:59 UTC
Created attachment 847781 [details]
File: proc_pid_status

Comment 11 Alois Mahdal 2014-01-09 19:25:00 UTC
Created attachment 847782 [details]
File: var_log_messages

Comment 12 Alois Mahdal 2014-01-09 19:25:04 UTC
Created attachment 847783 [details]
File: mousepad-crashfile.txt.gz

Comment 13 Alois Mahdal 2014-01-09 19:49:01 UTC
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.

Comment 14 Kevin Fenzi 2014-01-09 21:54:56 UTC
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?

Comment 15 Alois Mahdal 2014-01-10 09:33:54 UTC
> ...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.

Comment 16 Fedora End Of Life 2015-05-29 10:24:48 UTC
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.

Comment 17 Fedora End Of Life 2015-06-30 00:50:32 UTC
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.