Memory Leak on Apple M2 Max

[Choodz]

Description
The memory use increases with time. At launch, memory use is approximately 2 GB. After four hours, this had exceeded 10 GB. This was confirmed by checking Activity Monitor periodically.

To Reproduce
Use RuneLite with 117 HD plugin activated for an extended period of time.

Expected behavior
Memory use should not significantly increase with time.

Screenshots
This screenshot of Activity Monitor was captured after ~4 hours of RuneLite w/ 117 HD runtime:

Environment (please complete the following information):

• OS: macOS Ventura 13.2.1
• RuneLite version: 2.6.3 (Apple Silicon)

Additional context
RuneLite itself has been ruled out as a culprit after running it in "Safe Mode" which de-activates 117HD by default.

[aHooder]

Interesting. A few questions:

1. Do you have any other plugin hub plugins installed?
2. Are you launching RuneLite with the standard launcher & default launcher memory settings?
3. Does this also happen with RuneLite's GPU plugin?

This could be a bug with Apple's OpenGL driver, but we'd have to dig into it further to say for sure.

[Choodz]

Thanks for the response, @aHooder. To address your questions:

1. The only other plugin hub plugins installed are Quest Helper, Left Click Dropper, and Ping Graph.
2. I am launching with the default launcher and memory settings.
3. This would need to be tested -- I will try running for an extended period with GPU as opposed to 117HD and compare the results. I will be sure to report back with what I find.

[Choodz]

I have tested memory use with the GPU plugin. After extended use (about ~7 hours with the client open, although it auto-logged out and my Mac went to sleep for a short time - about four hours of continuous use at the end) memory use stands at 2.39 GB. Upon launch, memory use is about 950 MB.

So there is a memory leak phenomenon happening with the GPU plugin itself as well, albeit on a much less intensive scale than 117HD. Of course, 117HD is much more memory intensive, but I don't know if it scales compared to the GPU plugin.

As stated above, 117HD launches at ~2GB of memory, and rises to >10GB within four hours. The GPU plugin only doubled in the same time frame.

[aHooder]

Ah, thanks for looking into it. I would hazard a guess at it being caused by Apple's OpenGL driver not cleaning up after itself, but it's hard to say without looking at the raw data (and even then it would be tricky). Do let us know if you find any particular setting causes it to get worse though.

[TheGreatestJannet]

Same issue on Linux. I have had it go up to 18.5GB of RAM used. With the plugin enabled the RAM usage slowly goes up. With it disabled it stays at 1GB.

[aHooder]

Same issue on Linux. I have had it go up to 18.5GB of RAM used. With the plugin enabled the RAM usage slowly goes up. With it disabled it stays at 1GB.

I'm not able to reproduce this on Linux with proprietary Nvidia drivers. Which drivers and GPU are you using? And what time scale approximately?

[TheGreatestJannet]

I’m using Nvidia proprietary drivers (530.41.03) with a GTX 1060 6GB. After around 4 minutes it is already at 4GB and then slowly goes up from there. Yesterday I had been playing for probably one hour or so and it was at 18.5GB. The same time with the normal GPU plugin it was at 1.5GB of RAM.

[aHooder]

Are you sure this isn't just the model cache filling up? On my system, the base game uses roughly 2GB, and the model cache adds on top of that once it's filled up. What's your cache size set to?

[curxxx]

I can confirm there is still indeed a memory leak in 117HD on my M4 Mac. It's not the game cache.

While using the GPU plugin exclusively, my computer never exceeds 3GB of RAM usage; however, with 117HD enabled, eventually, it will use infinite amounts of RAM (I've seen as much as 20GB before I had to close it). This occurs even while logged out and idle on the log-in screen.

However, I'm not sure how to provide you with any additional info to help. I can take a memory sample of the app using Activity Monitor if that helps?

[SirFancyBacon]

Any and all information would help friend! None of us have an M# based Mac.

Our main dev is busy at the moment; but we will try to resolve it as quickly as we are able.