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

Memory leaked. Bug or not. #1391

Open
Pilad opened this issue Feb 12, 2018 · 5 comments
Open

Memory leaked. Bug or not. #1391

Pilad opened this issue Feb 12, 2018 · 5 comments
Labels

Comments

@Pilad
Copy link

Pilad commented Feb 12, 2018

If you set the render distance to 32, the maincraft sits completely in memory. The internal server is heavily loaded. In the 32pre2, this process is very fast. It takes 5-10 seconds. on the 32pre1 version this process is less fast.

@draknyte1
Copy link
Collaborator

draknyte1 commented Feb 12, 2018

Vanilla doesn't even allow > 16.
So, try without Optifine.

Then, maybe provide us with version numbers for Forge, Optifine, IC2, etc.

@draknyte1 draknyte1 added the bug label Feb 12, 2018
@Pilad
Copy link
Author

Pilad commented Feb 12, 2018

Last builds: Forge 1614 , OptiFine_1.7.10_HD_U_E3 , industrialcraft-2-2.2.828-experimental. GT 32pre1/pre2 use. Do you need something else?

@draknyte1
Copy link
Collaborator

Both Pre1 and Pre2 are horribly broken, so keep that in mind.
Pre2 mostly due to #1389.

Let me know how you go without Optifine.

@Pilad
Copy link
Author

Pilad commented Feb 12, 2018

Without Optifine in the same way. At the render distance 32, eats memory.

@Blood-Asp
Copy link
Owner

Now what exactly changes about rendering beween pre1 and pre2?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants