loftar wrote:boshaw wrote:It is odd, and it's the only thing i've ever noticed it on. Also, it's actually not at least in the constrained jvm heap itself after just checking. That seems to be within reasonable sizes after looking at the dumps, the process itself tho as a whole just is consuming and requesting more and more memory. Guessing it's just some bug in the runtime or something it has loaded outside of your control. Just from testing my process went from under 500mb to basically trying to consume all the RAM available over the course of a minute, but the heap itself was still normal sized.
Unfortunate. That makes it even more difficult for me to debug. Does it make a difference what browser Discord is running in ("native" app, Chrome, Firefox, &c)?
It does actually. I usually only use the native app, which has the problem, but it seems from in the browser (firefox & chrome in this case) it works fine.
Also here's one more little detail that seems to maybe pin down what's wrong with the native app at least. If you stream with "Also share application audio" it consumes memory at an insane rate, but if you turn that off it's just fine it appears. So it's something with the native app + audio being shared. Once you do make the mistake of doing that even when you stop the stream the java process still spirals out of control with consuming memory.