EngineHub / EngineHub/CommandBook

Thread leak - "Java Sound Manager"

Open
#25 2 comments 0 reactions 0 assignees View on GitHub
Accepted Bug Urgent
Dominant language
Java
Stars
151
Forks
104
PR merge metrics
No merged PRs in 30d

Description

Hello,

While debugging my own plugin, i added a command to monitor the threads used by bukkit and all the plugins.
I saw something strange in the output of the command, about 200 "java.util.Thread" called "Java Sound Manager".

So i did some tests with a vanilla server, a craftbukkit server without plugins and after i added all the plugins one by one.

Finally it seems that this kind of Thread is created by CommandBook.

Each time a player logged on the server, a Thread "Java Sound Manager" is created, but this thread is never destroy when the player logout. So after a few hours, depending on how many players you have on your server, you have a lot of useless threads still running :/

Like you said in your code comment in MidiJingleSequencer : " Sounds like utter crap" ^^

Tikkub

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.