CPU 100% occupied after running rocketmq console for several days

After running rocketmq console for several days (such as two or more days ) ,the CPU which was running the rocketmq console java thread turns to 100% occupied, in the meanwhile the dashboard json files have no longer to be updated under the location ../rocketmq console/data/, anyone can help to reslove the issue?
thanks so much!

Start by reproducing the long-running RocketMQ console behavior and inspect the Java thread when CPU reaches 100%. Check whether dashboard JSON files under ../rocketmq console/data/ stop updating, then use the captured thread activity and update behavior to identify the failure. Done means the console remains responsive and the dashboard files continue updating after several days.

Written by the indexing model from the issue text.