-
Notifications
You must be signed in to change notification settings - Fork 4
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
Refuses to run #43
Comments
Thanks for the catch: Noted the NullPointerException, found the issue causing it and committed fixes. This may or may not be related to the showstopper at the bottom. Running out of memory is not realistic; clearly a malfunction in the program. You're using the same GPU as before? If you can, please fetch to the newest update from git and clean install, let me know if the issue persists. I've added a log dump feature to trcl which will dump all of the errors and messages to log.html which can be attached to this bug report. Often critical errors are caused by states created by less-critical errors early in the program's loading process. |
Now, It won't even get two seconds into it. G:\sourcecode\TerminalRecall\terminal-recall>java -jar .\target\runme.jar STARTU |
Are you running from a 32-bit OS? It looks like you might be low on allocatable memory. G:\sourcecode\TerminalRecall\terminal-recall>java -Dorg.jtrfp.trcl.bypassConfigure=true -jar .\target\runme.jar STARTUP.POD FURY3.POD TERRAN.LVL |
If you continue to get the error with the above, do you get the error when you run: java -version ? Also, check if you have stray java processes running. When TRCL crashes the OpenGL threads sometimes get stuck which might be eating up your RAM. If you can't tell which java process is TRCL try rebooting. There were recent commits to help mitigate this but the issue is still being explored. |
java version "1.7.0_51" |
Check for stray java processes from half-crashed TRCL runs. They might be eating up your ram. |
There are no stray processes, and I have 8gb of RAM with 78% of it free. |
When I switch to the 64-bit version of Java, it works, but very slowly. Performance is really spotty, and the whole issue where smoke caused a lot of slowdown is back. It always worked fine on the 32-bit version up to this point, where it now refuses to launch entirely. |
Issue #44 has been created to address changes in framerate. |
I decided to compile Terminal-Recall after a very long period of time away... and I can't get it to run anymore. This is the output:
The text was updated successfully, but these errors were encountered: