-
Enhancement
-
Resolution: Fixed
-
P3
-
8
-
Windows, OS X and Linux
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8132178 | 7u40 | Alexander Matveev | P3 | Closed | Fixed |
Explicit dispose() method is needed to free native resources used by MediaPlayer. Garbage collector is not reliable enough to free native resources fast enough, thus when MediaPlayers are created fast enough we may run out of native memory. Normally, user does not need to call dispose() method on MediaPlayer if application does not create them often. After dispose() is called MediaPlayer cannot be used again and should be disregarded. Media and MediaView associated with disposed MediaPlayer can be reused. Dispose() will be valid in any states. For example, when player is playing call to dispose() will stop playback and release all resources.
- backported by
-
JDK-8132178 Add explicit dispose() method to MediaPlayer
-
- Closed
-
- relates to
-
JDK-8120882 Crash while using extended Seek While Scroll on Windows for MediaPlayer
-
- Resolved
-
-
JDK-8123986 JavaFx MediaPlayer not release the file handle for the file it played Window specific
-
- Resolved
-
-
JDK-8124054 Application crashes on random loading of media file
-
- Resolved
-
-
JDK-8125133 JavaFx Application crashes
-
- Resolved
-
-
JDK-8128496 Possible leak while playing video in a loop using JavaFX 2
-
- Resolved
-
-
JDK-8094930 Memory-Leak in Media Components
-
- Closed
-
-
JDK-8120818 Memory leak with media objects
-
- Closed
-
-
JDK-8118236 Runtime crashes with an EXCEPTION ACCESS VIOLATION after playing a video and then loading other URLs
-
- Closed
-
-
JDK-8120263 Too many open files and Memory leak
-
- Closed
-