forked from MultiMC/Launcher
-
Notifications
You must be signed in to change notification settings - Fork 154
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
Random Null Pointer Exception #80
Labels
bug
Something isn't working
Comments
Hm, this maybe also happens on upstream? Unsure though. |
I'll check if it happens in the new one. |
still happens on newest |
Update: attached backtrace |
According to the backtrace, it's likely that it also happens on the upstream launcher |
I don't think it does, asked a few people. |
Ok can replicate. |
Not sure what caused it, but it's fixed now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Operating System
Windows, Linux
Description of bug
When using a prelaunch command, certain things can cause crashes.
Backtrace:
Steps to reproduce
Edit Instance
>Settings
>Custom commands
.Custom commands
.cmd
orbash
orzsh
or any other command.Now it should crash. After this, relaunch MultiMC and disable
Custom commands
. Run the instance once and close it. Then enable them and it should work fine. If you restart MultiMC or use another instance the issue should occur again.Suspected cause
No response
This issue is unique
The text was updated successfully, but these errors were encountered: