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

Immersive Tech Boiler Crash Loop #1250

Closed
FantomBoGI opened this issue Apr 1, 2018 · 9 comments
Closed

Immersive Tech Boiler Crash Loop #1250

FantomBoGI opened this issue Apr 1, 2018 · 9 comments
Labels
Milestone

Comments

@FantomBoGI
Copy link

Whenever i load up my world it crashes.

I'm in age 3 and have done almost everything up to getting propene.

https://pastebin.com/F9pQ9QGv

@falloutfan576
Copy link

have you tried allocating more ram?

@CrypticDivide
Copy link

It is not a RAM issue.

From the linked crash report...
Memory: 2222482888 bytes (2119 MB) / 4771020800 bytes (4550 MB) up to 8392802304 bytes (8004 MB)

@falloutfan576
Copy link

Do not report to Forge! Remove FoamFixAPI (or replace with FoamFixAPI-Lawful) and try again. (foamfix-0.9.5-1.12.2-anarchy.jar) it might be a problem with FoamFixAPI then from this line in the crash report

@CrypticDivide
Copy link

CrypticDivide commented Apr 1, 2018

@falloutfan576 That is always generated in the crash report when FoamFixAPI is present. That does not always mean that FoamFixAPI is the underlying issue.

@sarcastic6
Copy link

This looks a lot like this issue: FerroO2000/Immersive-Tech#42

@artdude543
Copy link
Contributor

Yeah, this is an ongoing issue with the mod. I've asked them to try and look into it as it's showing up a lot more now.

@artdude543
Copy link
Contributor

There was a commit to fix the issue; awaiting that release (but from testing of a compiled build) it seems to fix the issue.

@justinrusso
Copy link
Member

This will be in the release for 3.0.7. Let us know if this fixes the issue

@justinrusso justinrusso changed the title Crash Loop Immersive Tech Boiler Crash Loop Apr 22, 2018
@justinrusso
Copy link
Member

If this issue persists in the next update, please submit a new issue. In testing this seems OK, but we were not able to replicate it initially.

@lock lock bot locked as resolved and limited conversation to collaborators Jul 9, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

6 participants