Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8093636

[media] Native memory leaking until nio.Buffers are GC'ed

    Details

      Description

      After a number of opening/disposing very long media files we may run out of the native memory while the Java heap is almost free. That leads to inability to open a media until the first full GC. No crashes observed.

      When the moov table is parsed the qtdemuxer asks to read that table in a single block. For 12hr mp4 that requires about 50Mb. The stream java source allocates direct ByteBuffer when asked for readBlock(). For reading the moov table the direct ByteBuffer of 50Mb is allocated. The problem is that this native memory could be released only when the instance of this ByteBuffer is garbage collected and thus native memory may leak even if the MediaPlayer.dispose() is called when closing media.
      Since there is no API for controlling media source stream operations the only workaround is to call System.gc() after MediaPlayer.dispose(), though no guarantees here of course.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                anashaty Anton Nashatyrev (Inactive)
                Reporter:
                anashaty Anton Nashatyrev (Inactive)
              • Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Imported: