Skip to content
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

Closed
Breitschwert opened this issue Jun 30, 2016 · 6 comments
Closed

Client Memory Leak #392

Breitschwert opened this issue Jun 30, 2016 · 6 comments
Labels
Priority: Critical Urgent issues that need immediate attention.

Comments

@Breitschwert
Copy link

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.

@Breitschwert Breitschwert changed the title Memory Leak Client Memory Leak Jun 30, 2016
@noblackthunder
Copy link

how much ram are we talking about ? towards the end i mean in usage from the client?

@noblackthunder noblackthunder added the Priority: Critical Urgent issues that need immediate attention. label Jun 30, 2016
@noblackthunder
Copy link

add coment / issue link. same cause ? #261 (comment)

@Breitschwert
Copy link
Author

Breitschwert commented Jun 30, 2016

Around 4GB was used. It started at below 2GB, accounting for already being joined to a server and after the initial memory growth phase. Then it slowly keeps growing after that.

The client without anything else is below 300MB, growing very slowly.

ecomemory

@Breitschwert
Copy link
Author

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.

@keegan-o
Copy link

keegan-o commented Jul 1, 2016

Happens for me too, with 16GB of memory.

@Breitschwert
Copy link
Author

Breitschwert commented Jul 3, 2016

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).
At the start, when the client just started, it is very responsive and works very well. There is no pause and shoveling works flawlessly.
The longer you play, the more of a delay occurs between the animation of the shovel+shoveling sound and the item that should spawn into your inventory. The delay can grow up to several seconds, before the item becomes available and the client freezes completely meanwhile.

Edit:The same thing occurs with chopping wood blocks from a tree and trying to take them into your inventory.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority: Critical Urgent issues that need immediate attention.
Projects
None yet
Development

No branches or pull requests

3 participants