Public bug reported:

Binary package hint: mediatomb

mediatomb memory usage grows extremely rapidly when I scan a directory
containing a large m2ts file, and eventually causes an OOM.

I'm initially setting up mediatomb with an existing pile of media, and I
set mediatomb to autoscan the media directory. Via top, the resident
size usually hovers anywhere between 30 and 50 MB. However, it
eventually starts growing very rapidly, reaching 1.5 GB in a matter of
seconds, and since I am running on a system with 2 GB of memory and no
swap, the kernel kills it (and sometimes something else) shortly
thereafter.

>From experimentation I found that a directory with a 17 GB m2ts file
from a Bluray disc was where things went south. Removing the directory
eliminates the problem. (I wish I'd remembered to try just removing the
file, but I do have plenty of other media files in the 1-4 GB range that
seem to pass through with no problems.)

I am running Ubuntu 10.04.1 LTS (release 10.04).
The version of the package is 0.12.0~svn2018-6ubuntu2.
I expected mediatomb to scan the media directory without causing an OOM (and 
ideally without moving out of its usual 30-50 MB memory footprint.)

** Affects: mediatomb (Ubuntu)
     Importance: Undecided
         Status: New

-- 
mediatomb on lucid OOMs with large m2ts file
https://bugs.launchpad.net/bugs/612855
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to