Closed MrWrightD7A closed 2 months ago
Thanks for reporting this issue. To facilitate our issue investigation from AMD OpenGL driver perspective, could you share the save file for us to reproduce your issue ?
Thanks for reporting this issue. To facilitate our issue investigation from AMD OpenGL driver perspective, could you share the save file for us to reproduce your issue ?
Thank you for bringing attention to this problem! I'm just not sure what you mean by ‘save file’. Do you mean the Minecraft map file, or something else? Simply, I encountered this problem exactly in Minecraft Beta 1.7.3 - both when playing on a multiplayer server and in single-player)
@MrWrightD7A Yes, Minecraft map file that can be loaded to reproduce the issue with the same exact level/map/world as yours
All right. Here you go. Run it on Minecraft Beta 1.7.3. New World.zip P.S. The problem with abnormal RAM/VRAM consumption in older versions of Minecraft is observed from AMD Adrenalin 22.7.1 Optional driver version to all the latest versions.
All right. Here you go. Run it on Minecraft Beta 1.7.3. New World.zip P.S. The problem with abnormal RAM/VRAM consumption in older versions of Minecraft is observed from AMD Adrenalin 22.7.1 Optional driver version to all the latest versions.
Thanks. We have successfully reproduced this issue, and the root cause is understood. A driver fix will be verified which will be included into future Adrenalin driver releases.
All right. Here you go. Run it on Minecraft Beta 1.7.3. New World.zip P.S. The problem with abnormal RAM/VRAM consumption in older versions of Minecraft is observed from AMD Adrenalin 22.7.1 Optional driver version to all the latest versions.
Thanks. We have successfully reproduced this issue, and the root cause is understood. A driver fix will be verified which will be included into future Adrenalin driver releases.
Well done! Thank you for your attention and work on this problem!
Good afternoon! I updated to a new driver version - 24.7.1. Unfortunately, the problem still remains(
But! If before (on drivers before version 24.7.1) RAM was clogged after 15-20 minutes approximately, now this time has increased. Now, on driver version 24.7.1, the memory fills up in 30-40 minutes.
Good afternoon! I updated to a new driver version - 24.7.1. Unfortunately, the problem still remains(
But! If before (on drivers before version 24.7.1) RAM was clogged after 15-20 minutes approximately, now this time has increased. Now, on driver version 24.7.1, the memory fills up in 30-40 minutes.
Hi, the fix is not yet included into the Adrenalin driver releases
Good afternoon! I updated to a new driver version - 24.7.1. Unfortunately, the problem still remains( But! If before (on drivers before version 24.7.1) RAM was clogged after 15-20 minutes approximately, now this time has increased. Now, on driver version 24.7.1, the memory fills up in 30-40 minutes.
Hi, the fix is not yet included into the Adrenalin driver releases
Okay, I get it. So the fix will be in the next driver release (after 24.7.1)?
Hi, the fix is not yet included into the Adrenalin driver releases
Okay, I get it. So the fix will be in the next driver release (after 24.7.1)?
I will notify you if I get any update on this.
Good afternoon! I updated to a new driver version - 24.7.1. Unfortunately, the problem still remains( But! If before (on drivers before version 24.7.1) RAM was clogged after 15-20 minutes approximately, now this time has increased. Now, on driver version 24.7.1, the memory fills up in 30-40 minutes.
Hi, the fix is not yet included into the Adrenalin driver releases
Okay, I get it. So the fix will be in the next driver release (after 24.7.1)?
The fix is expected to land in 24.8.1 Adrenalin release. Please check it out later on.
@MrWrightD7A The fix is rolled into Adrenalin 24.8.1 release already: https://www.amd.com/en/resources/support-articles/release-notes/RN-RAD-WIN-24-8-1.html. Could you verify this issue with this new driver release ?
@MrWrightD7A The fix is rolled into Adrenalin 24.8.1 release already: https://www.amd.com/en/resources/support-articles/release-notes/RN-RAD-WIN-24-8-1.html. Could you verify this issue with this new driver release ?
Hello. Okay, I'm going to test how this new driver version works with the game. I will report the results soon.
@DonglinWei2018 When installing the driver version that you have linked to, error number 182 is displayed. Even after using the AMD Cleanup utility, the error does not disappear.
@MrWrightD7A The latest driver is Adrenalin 24.10.1, does the "Abnormally increasing RAM consumption" issue disappear on the latest driver ?
Good afternoon, everyone!
During game sessions in Minecraft Beta 1.7.3 (using Java there is an abnormal increase in the game's RAM consumption. The growth is gradual: every 1-2 seconds the game "eats" 10-50 or even 100 megabytes of RAM. Which then, in the end, after 15-20 minutes, leads to the game hangs and the laptop RAM filled to the ceiling.
I asked the administration of the server (on which I play this version of Minecraft) on this matter. They replied that it might be due to a memory leak in the AMD driver. But we decided to try to fix this problem ourselves, having tried all possible solutions: from game settings/JVM-arguments to driver settings. But nothing helped - the game continued to "eat" memory.
Then I decided to try running the game on a Linux Mint distribution with all the latest updates and drivers. And strangely enough, Minecraft didn't even try to "eat up" the whole memory. Its RAM consumption was kept at the level of 600-800 megabytes and no more. That is, the problem (probably) is really in the AMD driver on Windows (because everything works perfectly under Linux).
Also, I decided to try rolling back from the new version of AMD driver for Windows to the old one - no result. Also, I asked other server players, who like me play on laptops/computers with integrated AMD video chips - the problem is the same for all of them. But only one of them, who had an old version of the driver (30.0.14023.7007), had everything normal and the game did not "eat up" the whole memory. But I decided not to install (for now) the version of the driver on which the last mentioned player is playing.
Of course, I reported this problem via AMD Bug Report Tool as well. But additionally, to speed up the process somehow, I decided to share it on the forum. Maybe someone else has also encountered a typical unpleasant mishap...
Laptop Characteristics:
Thanks for your attention!