vlcj-player | Feature-rich example vlcj media player | Video Utils library

tldr;

Add Thread.currentThread().join(); after calling play method of media player inside the class hosting the callback. It will somehow keep the thread running, preventing the execution stopping due to end of executable logic in case any native lib error.

After doing many experiments or say trial and error, I found this.

Something else needed to keep the application running or otherwise even a single error in native code while processing the stream will kill the whole application. The actual code from where I took usage example of custom renderer is opening a jwt Frame which is keeping the application open. I removed it as I need not to show anything. But, now I started getting the problem. There's no other work left for the running thread/class, any error originating in native lib will break the connection(an expert might use a better terminology here) and hence the program will close, in return JNI will fire callback object is garbage collected.

I was using the Thread.currentThread().join(); but outside the class after creating an instance, hence effecting nothing for the class hosting the callbacks for rendering/processing the data.

Thinking more about what the jwt Frame might be doing, I removed it and replaced with Thread.currentThread().join(); inside the constructor, voila it started working perfectly.