-
Bug
-
Resolution: Invalid
-
None
-
Minecraft 1.13.2, Minecraft 19w03b
-
None
-
java version "1.8.0_191"
Java(TM) SE Runtime Environment (build 1.8.0_191-b12)
Java HotSpot(TM) 64-Bit Server VM (build 25.191-b12, mixed mode)
OS Name: Microsoft Windows 10 Pro
OS Version: 10.0.17134 N/A Build 17134
OS Manufacturer: Microsoft Corporation
OS Configuration: Standalone Workstation
OS Build Type: Multiprocessor Free
System Manufacturer: Gigabyte Technology Co., Ltd.
System Model: X470 AORUS ULTRA GAMING
System Type: x64-based PC
Processor: AMD Ryzen 7 2700X Eight-Core Processor (16 CPUs), ~3.7GHz
[01]: AMD64 Family 23 Model 8 Stepping 2 AuthenticAMD ~3700 Mhz
Total Physical Memory: 32,713 MB
Virtual Memory: Max Size: 39,974 MB
Card name: NVIDIA GeForce GTX 1080
Manufacturer: NVIDIA
Chip type: GeForce GTX 1080
DAC type: Integrated RAMDAC
Device Type: Full Device (POST)
Display Memory: 24435 MB
Dedicated Memory: 8079 MB
Shared Memory: 16356 MB
Current Mode: 1920 x 1080 (32 bit) (60Hz)
HDR Support: Not Supportedjava version "1.8.0_191" Java(TM) SE Runtime Environment (build 1.8.0_191-b12) Java HotSpot(TM) 64-Bit Server VM (build 25.191-b12, mixed mode) OS Name: Microsoft Windows 10 Pro OS Version: 10.0.17134 N/A Build 17134 OS Manufacturer: Microsoft Corporation OS Configuration: Standalone Workstation OS Build Type: Multiprocessor Free System Manufacturer: Gigabyte Technology Co., Ltd. System Model: X470 AORUS ULTRA GAMING System Type: x64-based PC Processor: AMD Ryzen 7 2700X Eight-Core Processor (16 CPUs), ~3.7GHz [01]: AMD64 Family 23 Model 8 Stepping 2 AuthenticAMD ~3700 Mhz Total Physical Memory: 32,713 MB Virtual Memory: Max Size: 39,974 MB Card name: NVIDIA GeForce GTX 1080 Manufacturer: NVIDIA Chip type: GeForce GTX 1080 DAC type: Integrated RAMDAC Device Type: Full Device (POST) Display Memory: 24435 MB Dedicated Memory: 8079 MB Shared Memory: 16356 MB Current Mode: 1920 x 1080 (32 bit) (60Hz) HDR Support: Not Supported
-
Confirmed
Steps to reproduce (vanilla)
Steps to reproduce (modded server)
I would not submit a bug report if this was a server side memory leak. This is a client-side memory leak. I do not know if this has to do with pushing texture data for mini-maps when changing items on the ItemFrame, or if the metadata stores native item stacks in some way that is building up.
The way to reproduce the memory leak is to send repeated changes to ItemFrames with item data, linking to pre-existing map ID's that are already sent to the player. I did this using Spigot's API and sending a series of 10 128x128 static mini-maps, repeatedly changing each ItemFrame every 10 ticks (1/2 second).
For some reason, this causes the client's RAM allocation to jump dozens of megabytes per update (16x9 ItemFrames).
This is what the board looks like. The board occasionally updates with invisible mini-maps every 5 or so updates, however I could assume that to be an issue with anything outside of the original minecraft code as I have fixed this using NMS packet code, although it may be worth noting.
- relates to
-
- Resolved
- links to