Skip to content

Conversation

@3arthqu4ke
Copy link
Member

@3arthqu4ke 3arthqu4ke commented May 15, 2025

Micro-Optimization, was not really worth it.

Only worth it when a fresh instance of Mc is started, in that case all the library/asset downloading threads seem to fill up the memory?

@3arthqu4ke 3arthqu4ke linked an issue May 15, 2025 that may be closed by this pull request
@github-actions
Copy link

Overall Project 71.49% -0.42% 🍏
Files changed 36.4%

File Coverage
Main.java 96.45% -1.42% 🍏
Main.java 86.84% -10.53% 🍏
AbstractLaunchProcessLifecycle.java 68.47% -7.01%
ProcessThread.java 17.09% -82.91%

@github-actions
Copy link

Overall Project 71.48% -0.42% 🍏
Files changed 35.97%

File Coverage
Main.java 96.45% -1.42% 🍏
Main.java 86.84% -10.53% 🍏
AbstractLaunchProcessLifecycle.java 68.17% -7.41%
ProcessThread.java 17.09% -82.91%

@3arthqu4ke 3arthqu4ke merged commit d3b6a90 into main May 15, 2025
1 check passed
@3arthqu4ke 3arthqu4ke deleted the 281-optimize-memory-footprint branch May 15, 2025 01:33
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

Successfully merging this pull request may close these issues.

Optimize Memory footprint

2 participants