Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
MythicDungeons MythicDungeons
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 84
    • Issues 84
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • MythicCraft
  • MythicDungeonsMythicDungeons
  • Issues
  • #235

Closed
Open
Created Apr 02, 2023 by jahua50@jahua50

Possible memory leak issue + encountered queue issue

Hi MD developers, I have been encountering some possible memory leak issues. I used a test server to test it. When I open and close dungeon over a specific times, the server will crash due to outofmemory error. The only plugins I installed are md and protocollib. I used paper 1.19.2 build 173 and 1.19.3 build 448 and md build 135 for testing. The logs are here: https://pastebin.com/pauDgDjp

For the queue issue, our players reported that sometimes the queue system would stuck, and no one can enter the dungeons or leave the queue. Our server limited 6 instances max. The normal queue situation is: player gets in queue -> player notified that theres a instance limit -> the ready info jumps out(when a instance is freed) -> get in the dungeon normally When a stuck happens: player gets in queue -> player notified that theres a instance limit -> stays in the queue even someone has finished a dungeon.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking