Bug 376462 - konsole stops displaying output after too much
Summary: konsole stops displaying output after too much
Status: RESOLVED DUPLICATE of bug 372991
Alias: None
Product: konsole
Classification: Applications
Component: general (show other bugs)
Version: 16.12.2
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-02-13 22:50 UTC by Hello71
Modified: 2017-02-15 00:59 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Hello71 2017-02-13 22:50:50 UTC 
Steps to reproduce:

1. i=0; while :; do ((i++)); printf '%d\r' $i; done
2. Press Ctrl-C.
3. Type "exit" and press enter.

Expected results:

After 1. terminal prints increasing numbers.
After 2. terminal prints shell prompt.
After 3. terminal closes.

Actual results:

After 1. terminal prints increasing numbers.
After 2. terminal displays last number printed, with cursor at start of line. no shell prompt is displayed, and typing produces no output.
After 3. terminal closes.
Comment 1 Kurt Hindenburg 2017-02-13 23:18:17 UTC 
Do you know if you have unlimited scrollbacK?  If so, after 2GB of scrollback, Konsole behaves badly.
Comment 2 Hello71 2017-02-13 23:49:22 UTC 
No, I set limited scrollback due to the excessively inefficient usage of RAM. Anyways, I cut it off after few hundred thousand, so that shouldn't be an issue.
Comment 3 Egmont Koblinger 2017-02-14 16:02:26 UTC 
I can reproduce it in about 1 out of 10 attempts.
Comment 4 Egmont Koblinger 2017-02-14 16:04:47 UTC 
Scrollback shouldn't matter (Kurt: note the '\r' in the output, this script just overwrites the number at a fixed location).
Comment 5 Kurt Hindenburg 2017-02-14 16:15:37 UTC 
I wonder if this is the same as https://bugs.kde.org/show_bug.cgi?id=372991 - that one is really confusing
Comment 6 Egmont Koblinger 2017-02-14 16:32:46 UTC 
Yeah they do sound the same.
Comment 7 Hello71 2017-02-15 00:59:57 UTC 

*** This bug has been marked as a duplicate of bug 372991 ***