Bug 17173

Summary:	klipper CPU loop
Product:	Mageia	Reporter:	Pierre Fortin <pf>
Component:	RPM Packages	Assignee:	KDE maintainers <kde>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	marja11
Version:	5	Keywords:	UPSTREAM
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
See Also:	https://bugs.kde.org/show_bug.cgi?id=33747
Whiteboard:
Source RPM:	kdebase4-workspace-4.11.16-5.mga5	CVE:
Status comment:

Description Pierre Fortin 2015-11-18 18:15:03 CET

Description of problem:  editing /var/log/messages with emacs for bug 17147. File contains entries from Aug to today. Selected all entries from beginning to first Oct entry (140,376 lines / 14,947,259 chars) and hit ctrl+w.

top:
32193 pfortin   20   0  570728  98964  29512 R  99.9  0.3  11:12.31 klipper

Killed it.

Restarted klipper & repeated edit:
20707 pfortin   20   0  406544 121728  29744 R 100.0  0.4   1:23.23 klipper


Version-Release number of selected component (if applicable):


How reproducible: always


Steps to Reproduce:
1. cause LARGE amount of data to be captured by klipper
2.
3.


Reproducible: 

Steps to Reproduce:

Comment 1 Marja Van Waes 2015-11-18 23:07:50 CET

See the upstream bug report, filed 14(!) years ago, from someone who tried something similar: 

> It would be nice to limit how much of the clipboard gets copied to the klipper.
> I often highlight a large amount of text in my emacs window sometimes megabytes
> worth. Even though it gets copied to the clipboard with no problems klipper
> chokes and freezes up kde while it's trying to copy the buffer. Usually I kill
> klipper until I'm doing with emacs cut&paste.
( https://bugs.kde.org/show_bug.cgi?id=33747 )

Keywords: (none) => UPSTREAM
CC: (none) => marja11
See Also: (none) => https://bugs.kde.org/show_bug.cgi?id=33747
Assignee: bugsquad => mageia

Samuel Verschelde 2016-08-25 16:23:27 CEST

Assignee: mageia => kde

Comment 2 Marja Van Waes 2018-04-27 16:18:52 CEST

Hi Pierre,

Thank you for having taken the needed time to report this issue!

We regret if this issue didn't get fixed.

Closing as OLD, because Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/
It only continued to get important security updates since then, but non-security bugs have no chance of still getting fixed.

Marja

Status: NEW => RESOLVED
Resolution: (none) => OLD