[BDS-14781] Memory leaks with bds version 1.17.11 or down Created: 16/Aug/21 Updated: 27/Jan/23 Resolved: 27/Jan/23 |
|
| Status: | Resolved |
| Project: | Bedrock Dedicated Server |
| Affects Version/s: | 1.17.11 Hotfix, 1.17.10 |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | fillJin | Assignee: | Unassigned |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | None | ||
| Environment: |
Windows Server 2019 and Windows 10, use bds official from website mojang. |
||
| Issue Links: |
|
||||||||
| Confirmation Status: | Unconfirmed | ||||||||
| Description |
|
there is a problem here is memory leaks, bds in the latest official version is currently having a pretty serious memory leak. The problem is that when I open bds for a long time, over time my server gradually lags, and the memory starts to increase little by little. I don't have pictures so I can only describe it in detail. I open in vps with Core 4 configuration - 16gb ram. When opening started with 45 players and was full but there was no lag, but about 1-2 hours later, there were signs of slight lag, memory also increased significantly from 1gb to increase. up to 3gb, until a certain time, even though there are very few people in the server, even about 10 people lag strongly. My solution for that is to restart the server periodically. I hope the publisher side can fix it in the next version and give me a positive feedback from the mojang side. |
| Comments |
| Comment by Maciej Piornik [ 27/Jan/23 ] |
|
Cleaning up old tickets: This ticket had been set to 'Awaiting Response', but has not received a response from the reporter (~3 months+) so is being closed as Incomplete. If you feel this is still a valid issue then please comment, or create a new ticket following the Issue Guidelines which includes steps to reproduce the problem. Quick Links: |
| Comment by Maciej Piornik [ 15/Dec/21 ] |
|
Hi Does this issue still occur after updating to 1.18.2? This ticket will automatically reopen when you reply. |
| Comment by fillJin [ 26/Nov/21 ] |
|
it didn't appear in version 1.17.34, but version 1.17.40 had this problem again |
| Comment by Maciej Piornik [ 07/Oct/21 ] |
|
Hi Does this issue still occurs after updating to 1.17.34? This ticket will automatically reopen when you reply. |