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.

Sign up for GitHub

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

Jump to bottom

NeoForge stale process require kill -9 to flush from memory. #1225

Open
leagris opened this issue Dec 22, 2024 · 5 comments
Open

NeoForge stale process require kill -9 to flush from memory. #1225

leagris opened this issue Dec 22, 2024 · 5 comments
Labels
Awaiting Reply bug Something isn't working

Comments

@leagris
Copy link

leagris commented Dec 22, 2024

What Operating System

Linux (Debian)

Debug Code

https://pste.ch/xamebarubu

Describe the bug

Neoforge 21.1.90 and earlier launched from FTBApp leaves a stale process with all its memory allocated in Linux.
A SIGKILL (normal kill) does not stop the stale java process. A kill -9 is required

Steps to reproduce

  1. Install and run ATM10 modpack on its required version of NeoForge.
  2. Quit the modpack
  3. Even quit FTBApp
  4. The NeoForge modloader process and all its ASM patches all with its entire allocated memory space is still there and the only way to get ride of it is ti kill -9 the stale NeoForge process.

Expected behaviour

Once the modpack is stopped, no process shall remain in memory.

Screenshots

No response

Additional information

No response
@leagris leagris added the bug Something isn't working label Dec 22, 2024
@leagris
Copy link
Author

leagris commented Dec 22, 2024

Reinstalled the pack entirely and the issue seems gone. I Will keep updates and close in a few days if confirmed solved

@leagris
Copy link
Author

leagris commented Dec 23, 2024

Today I got the NeoForge instance again not stopping after quitting the game.

Because I kept the FTB App running, I could use the Kill Instance button to stop the instance, otherwise I'd be stuck with a stale java process as stated in the description of this issue.

@MichaelHillcox
Copy link
Member

Can you confirm if you're running a modpack or not?

@leagris
Copy link
Author

leagris commented Dec 23, 2024

Can you confirm if you're running a modpack or not?

Running All The Mods 10

@MichaelHillcox
Copy link
Member

This will likely mean the issue comes from All The Mods 10 having a mod that blocks the full shutdown of Java. I'd recommend creating a fresh NeoForge instance and seeing if you can reproduce the issue on that instance

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Awaiting Reply bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@leagris @MichaelHillcox