Bug 18447

Summary:	Kaffeine update breaks ATSC recording
Product:	Mageia	Reporter:	Rolf Pedersen <rolfpedersen>
Component:	RPM Packages	Assignee:	All Packagers <pkg-bugs>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	marja11
Version:	5
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	kaffeine-1.3.1-1.mga5.src.rpm	CVE:
Status comment:
Attachments:	new kaffeine using up all the memory before crashing old kaffeine records both tuners for hours, no problem, as for years new kaffeine goes to swap, apparently

Description Rolf Pedersen 2016-05-12 17:36:36 CEST

For about 2 years, I've been using kaffeine to record over-the-air television, up to two programs at one time, with an Hauppauge HVR-2250 pci-e card on HP-GT7725. After update applet installed kaffeine-1.3.1-1, I began to see recordings did not finish and kaffeine had stopped running. Looking at

# journalctl | grep kaffeine

May 07 14:45:05 HP-Kodi kernel: [ 2237] 501 2237 1269468 844127 2288 7 133191 0 kaffeine
May 07 14:45:05 HP-Kodi kernel: Out of memory: Kill process 2237 (kaffeine) score 805 or sacrifice child
May 07 14:45:05 HP-Kodi kernel: Killed process 2237 (kaffeine) total-vm:5077872kB, anon-rss:3375896kB, file-rss:612kB

It prompts me to look at memory usage while the newer kaffeine is running. In htop I can watch while new kaffeine memory usage grows, more and more swap gets used, /tmp gets full, and, finally, kaffeine crashes. I'll upload a couple of screenshots of this displayed in htop, while old kaffeine records two programs simultaneously for hours, no memory problems, as it has done for years.

As I could get some memory for not much money, I increased ram from 2G (worked for years) to 4G. 256M are reserved for onboard memory. FYI, doubling the ram did not fix this regression in kaffeine.

This is a regression, isn't it? The previous kaffeine worked for years on the same hardware with less memory, so I thought that is what regression means. I found, in the changelog for the new kaffeine, that it had been pushed through to address https://bugs.mageia.org/show_bug.cgi?id=18039 and I commented there, as I was thinking it was a regression. However, I was told to make my own bug, so here it is.

Comment 1 Rolf Pedersen 2016-05-12 17:41:00 CEST

Created attachment 7784 [details]
new kaffeine using up all the memory before crashing

Comment 2 Rolf Pedersen 2016-05-12 17:44:25 CEST

Created attachment 7785 [details]
old kaffeine records both tuners for hours, no problem, as for years

Old kaffeine does what it has for years, recording two programs at the same time, no crashing, no problem.

Comment 3 Rolf Pedersen 2016-05-12 17:47:59 CEST

Created attachment 7786 [details]
new kaffeine goes to swap, apparently

I only see this swap usage while running new kaffeine and said usage goes down when new kaffeine is stopped.

Comment 4 Marja Van Waes 2016-05-12 19:17:25 CEST

Assigning to all packagers collectively, since there is no maintainer for this package.

CC: (none) => marja11
Assignee: bugsquad => pkg-bugs

Comment 5 Marja Van Waes 2018-04-24 19:20:57 CEST

Hi Rolf,

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

We regret if this issue didn't get fixed in Mageia 5. I assume the problem doesn't exist in Mageia 6, because all of KDE is so different now. Don't hesitate to tell me if I'm wrong.

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

Comment 6 Rolf Pedersen 2018-04-25 03:12:18 CEST

Yes, Marja.  Since kaffeine-1.3.1, a lot of work has been done by Mauro Carvalho Chehab, Antoni Bella Pérez, and it seems others have joined the work of developing kaffeine 2, leaving 1.3 behind.  Once Mageia published Plasma 5, I've been able to enjoy all this continuing improvement, now with kaffeine-2.0.13-1, which is working very well, for my purposes, at least. ;)
Thanks.