Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
This bug (if it's the same one) appears to be Discord either keeping things in its own memory when it reads from Balatro, or doing something to Balatro's screen memory whenever it accesses it. Since it sounds like the people reporting it see Balatro's RAM usage go up in Windows' resource manager, probably the latter.
But when you record your entire screen, Discord doesn't access every program's memory to capture its graphical output, but just accesses the full frame the OS sends to the monitor. No weird memory interaction, no memory leak, no crash.