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

What bugs were fixed? #438

Closed
nazthelizard122 opened this issue Nov 26, 2020 · 3 comments
Closed

What bugs were fixed? #438

nazthelizard122 opened this issue Nov 26, 2020 · 3 comments

Comments

@nazthelizard122
Copy link

nazthelizard122 commented Nov 26, 2020

I noticed the launcher had an update I'm hopeful that the memleak is patched if not I'll write another issue I'm glad 1.16.200 works now but ill stick to 1.16.101 for now I just started afking if it crashes like I said I'd write another issue.

@nazthelizard122 nazthelizard122 changed the title What bugs were fixed What bugs were fixed? Nov 26, 2020
@ChristopherHX
Copy link
Member

ChristopherHX commented Nov 27, 2020

I fully discontinued my fork, ng is much different.
ng has two arm AppImages (lots of 0 changes for x86)

Theres is no known memleak in ng.
Ng has known instability, you have to deal with it.

@nazthelizard122
Copy link
Author

Cool, is there a fix for the instability?

@ChristopherHX
Copy link
Member

ChristopherHX commented Nov 27, 2020

I cannot follow you weird logic.
You can contribute a fix, if there weren't known instability then you wouldn't notice it.

My own fix is using my win10 edition, I got it for free from my ancient java premium account.

@trig02838 trig02838 mentioned this issue Nov 9, 2022
@mnkhprre mnkhprre mentioned this issue Dec 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants