-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Client Memory Leak #392
Comments
how much ram are we talking about ? towards the end i mean in usage from the client? |
add coment / issue link. same cause ? #261 (comment) |
Disconnecting from a server, after the memory has been filled up, frees about 500MB worth of memory and then it stays there. Right now, I am sitting at 4.758.732K filled, while it was above 5.000.000 when on a server. |
Happens for me too, with 16GB of memory. |
Shoveling is the most affected by this issue or maybe even a cause. The longer the client runs, the longer of a pause happens, when you try to shovel up an item (stone, dirt). Edit:The same thing occurs with chopping wood blocks from a tree and trying to take them into your inventory. |
Version: Alpha 04
Type: Client (local Server/Singleplayer and Online/other Server)
OS: Windows 7 64bit Home Premium
Detailed Description of Issue:
After running the game for a while, the memory usage becomes increasingly high, edging towards the maximum of the PC and causing Windows to throw error messages of no memory being available. It appears that there is a memory leak present in the client.
Reproducible? How difficult is it to reproduce?:
It always occurs, but takes quite some time to build up. Tried it three times with a local server as well as an online one.
Steps to reproduce bug/issue:
Run the game, check the memory usage after joining the server and play normally, as in craft, chop trees, gather fruits, etc. After a prolonged amount of time (1 hour), verify the memory usage by the client in Taskmanager. It should've significantly increased.
The text was updated successfully, but these errors were encountered: