Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 461626 - media-tv/tvbrowser-3.2.1: Sporadically high cpu load because of low maximum memory?
Summary: media-tv/tvbrowser-3.2.1: Sporadically high cpu load because of low maximum m...
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Java team
URL: http://forums.gentoo.org/viewtopic-p-...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-03-13 12:36 UTC by Small_Penguin
Modified: 2015-05-30 12:27 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Small_Penguin 2013-03-13 12:36:50 UTC
I had problems with tvbrowser often causing high cpu load sporadically. It is caused by max memory not set high enough, so I opened /usr/share/java-config-2/launcher/launcher.bash in the editor and added the -Xmx4096M parameter to the last line. The machine has 16GiB RAM. This definitely fixes the problem.

Please modify the launcher script so that tvbrowser can work without the garbage collector wreaking havoc all the time. I'm not sure how much memory is needed, in 2.7 256MiB has been the default according to the wiki, but I don't think this is valid in newer versions. Maybe 512MiB would be better or even enough, though I'm not sure. After using it for awhile (scrolling around etc.) RES quickly raises. Perhaps making that value optional so it can be configured in a file in /etc would be a good idea.


Reproducible: Always
Comment 1 Johannes Huber (RETIRED) gentoo-dev 2015-05-30 10:36:14 UTC
@Java if you are not interested in maintaining it, move it to maintainer needed.

+
+  30 May 2015; Johannes Huber <johu@gentoo.org> metadata.xml:
+  Remove myself as maintainer.
+
Comment 2 Small_Penguin 2015-05-30 12:27:02 UTC
This is no longer reproducible (tvbrowser-3.4.1.0). I am closing this bug.