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 problem occurs due to some kind of application conflict when using the game (nwjs on Chromimum) in parallel and running some services in the Chrome browser.
If you play the game and watch Twitch (they also complained about netflix), then the problem arises, and very quickly. I suspect that it is the browser that somehow fills the game's memory without clearing it.
The game does not physically have pictures and code for 3GB.
The solution so far is only using a different browser for these services than Chrome.
A similar topic in the CG3 game community.
http://www.matthewfarmery.net/screenshots/coloringgame.jpg
after 10 minutes of play, and already using nearly 1gig of ram. Only seems to go up when inside the program, if alt tabbed out, there is no change.
What is running in Chrome?
I have now actively tested the game twice (loading and painting the last ten pictures) for 15 and 10 minutes. Memory does not grow.
What video card and driver version do you have?
Last year there were complaints from users about a problem with AMD drivers.
also, Im using directory opus 12 for the windows explorer replacement. (not sure if that is the culprit? otherwise, not sure what else?
also got razor central running in the background, ESET security,
Cant think what else could be the problem?
Edit, I will try and update my geforce drivers and see if that helps.
Thanks for trying to help, not sure what else to really try.
In theory it should help if you add the NWJS process (executable game.exe) to the exclusion list.[help.eset.com]
This is certainly odd, as I would have thought this bug would have effected all your games, but it doesn't.
Edit, tried the largest image available in 4, and ram usage does climb. So yes, back to the drawing board.
Ah, that is interesting.