EngineHub / EngineHub/CommandBook

Thread leak - "Java Sound Manager"

未关闭
#25 2 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看
Accepted Bug Urgent
主要语言
Java
星标
151
派生
104
PR 合并指标
30 天内没有已合并 PR

描述

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

贡献指南

打开贡献指南

调研方向

从 issue 中引用的 MidiJingleSequencer 代码开始,在装有 CommandBook 的 vanilla 服务器上监控玩家登录和登出期间的线程,以复现该行为。完成的标准是玩家登出后不再留下不断累积的 "Java Sound Manager" 线程。

由索引模型根据 Issue 内容生成。

评估

技术栈
java
领域
backend
Issue 类型
缺陷
难度
3/5
预计耗时
1-2 天
活跃度
停滞
描述清晰度
基本清楚
新手友好度
38/100

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。