Bug 346794 - konsole crashes when selecting or pasting large amounts text
Summary: konsole crashes when selecting or pasting large amounts text
Status: RESOLVED FIXED
Alias: None
Product: konsole
Classification: Applications
Component: general (show other bugs)
Version: 15.04.0
Platform: Arch Linux Linux
: NOR major
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-04-27 14:39 UTC by ian
Modified: 2015-05-12 17:04 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Text where konsole crashes every time when pasting into a vim session (8.13 KB, text/plain)
2015-04-27 14:44 UTC, ian
Details
strace of a session that seg faults (2.25 MB, text/plain)
2015-05-12 10:38 UTC, ian
Details

Note You need to log in before you can comment on or make changes to this bug.
Description ian 2015-04-27 14:39:40 UTC
When selecting or pasting a large amount of text from or into from the console, konsole core dumps.  I have experimented and found that the crash seems to come when pasting or trying to select text with more than about 8328 characters (known value where konsole crashes every time).
I will attach a file where this happens every time to me.

Reproducible: Always

Steps to Reproduce:
For selection
1. Start selecting text, allow konsole to scroll through the history, it will crash after selecting sufficient characters.  The selection does not make it to klipper.

For Pasting
1. In vim, paste text that has more than 8328 characters, my test was over 112 lines.


Actual Results:  
core dump
Comment 1 ian 2015-04-27 14:44:27 UTC
Created attachment 92279 [details]
Text where konsole crashes every time when pasting into a vim session

When pasting this text into vim, konsole core dumps for me
Comment 2 Kurt Hindenburg 2015-05-10 14:53:34 UTC
It works here even w/ your attachment - what do you have your Scrolling->Scrollback set to?  Also are you using any input-methods?
Comment 3 ian 2015-05-11 12:32:54 UTC
My history for the default profile is set to 30000 lines.  Interestingly I can't find this in any configuration file anywhere.  I seem to not be able to find any configuration file anywhere for konsole which would correspond to the settings I have.  If you can help me find the right configration file I can add it to this.

In the meantime what I can tell you is
30000 fixed scroll size
show scroll bar on right side
scroll page up/down is full page.
I have a green on black and use a customised PS1 ${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$
Text is 9 point monospace
smooth fonts is on
Draw intense colours in bold is on
tripple click is set to select the entire line
Copy & paste, neither Copy on select nor trim trailing spaces is selected (both are off)
middle button action is paste from selection
Underline links is on, open links by click is off
require ctrl key for drag & drop is on
allow ctrl+scrollwheel to zoom text is on
allow blinking test is on
enable flow control is on
enable bidirectional flow text rendering is on
blinking cursor is on
cursor shape is block
set cursor colour to match text colour is on
default character encoding is utf-8

I am having troubles with knoqueror crashes too, for example on logging in to the bugs.kde.org site.  I wonder if there is a deeper seated problem to be found?
Comment 4 ian 2015-05-12 10:36:31 UTC
I have made an strace -f -ff of a konsole session which I will attach. Maybe this helps to trace the problem
Comment 5 ian 2015-05-12 10:38:08 UTC
Created attachment 92555 [details]
strace of a session that seg faults
Comment 6 ian 2015-05-12 12:31:46 UTC
I just tried downgrading konsole to konsole-14.12.3-1-x86_64.pkg.tar.xz.

From the Help/About konsole menu item:
Konsole
Version 3.0.1
Using KDE Frameworks 5.9.0

The coredumps still happen.  I am starting to suspect a deeper lying problem.
Comment 7 ian 2015-05-12 17:03:52 UTC
I just finished a complete update of my system.  The crash no longer happens.  I have tested with 1050000+ characters.
I guess it may have been an incompatilbe library or something similar.  In any case I will close the bug as being resolved.