Bug 64338 - amarok uses up all kern.maxfilesperproc
Summary: amarok uses up all kern.maxfilesperproc
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: Markus Brueffer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-03-16 13:10 UTC by Csaba Molnar
Modified: 2004-03-18 16:59 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Csaba Molnar 2004-03-16 13:10:16 UTC 
After starting up amarok, the kern.openfiles value begins to rise, until it reaches the maximum value (on my system, 9500). I choose the 'serious' severity, because this can lead to system freeze (recoverable by killing amarok), and a wide range of problems: for instance, it can prevent ipfw from creating new dynamic rules. This is how it looks like on my computer:
<< Mon Mar 15 03:19 PM>>
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2004-03-16 15:41:10 UTC 
Responsible Changed
From-To: freebsd-ports-bugs->markus

Over to maintainer.
Comment 2 Markus Brueffer freebsd_committer freebsd_triage 2004-03-16 21:35:35 UTC 
State Changed
From-To: open->feedback

I have tracked down what caused raising kern.openfiles. Basically the  
bug you found was triggered by another bug which didn't let the IPC 
initialize properly (and which wasn't known as well). 

Below are fixes for both bugs. Just place them into the files-directory 
of the amarok-port and reinstall amarok. Please let me know, if  
that solves the problem for you. 

http://www.brueffer.de/patches/patch-playerapp.cpp  
http://www.brueffer.de/patches/patch-loader.cpp 

Markus
Comment 3 Markus Brueffer freebsd_committer freebsd_triage 2004-03-18 16:57:47 UTC 
State Changed
From-To: feedback->closed

Patch which solves this committed. Thanks for reporting this bug!