here's what the end of the log looked like: mediaStateChanged I noticed two events received after finished: first mediaChanged, then newMedia. So I used an event listener which logged most events, and kept the Thread.sleep(1000) statement before player.release(). I then tried to add a Thread.sleep(1000) statement before player.release(), and I could no longer reproduce the crash. It sometimes worked, but most often raised an error : Invalid memory access on player.release(). Now, here are the details of my experiments. If that happens after releasing the player, it crashes.

Tl dr: After the finished event, VLC still fires two other events: mediaChanged and newMedia. I think I was able to answer my question, thanks to caprica's comments. The rest of the crash log can be seen here.

# See problematic frame for where to report the bug. # The crash happened outside the Java Virtual Machine in native code. # If you would like to submit a bug report, please visit:

To enable core dumping, try 'ulimit -c unlimited' before starting Java again # Java VM: Java HotSpot(TM) 64-Bit Server VM (25.121-b13 mixed mode bsd-amd64 compressed oops) # A fatal error has been detected by the Java Runtime Environment: The transcoding finishes succesfully, but on player.release(), the JVM crashes with a SIGSEGV error: # The transcoding seems to be working fine, but I'm getting an error when releasing the MediaPlayer.īellow is my minimal test code, based on the RipAudioTest from the VLCJ repo: public class VlcjTestMain ' I'm on OS X 10.11.6 with Java 8u121, and I'm trying to use VLCJ 3.10.1 (with VLC 2.2.4) to transcode an audio file (from MP3 to OGG Vorbis).

Oops vlc media player just crashed