Example of crash with Mekanism
Issue can be resolved by removing "-DFORGE_FORCE_FRAME_RECALC=true" from the VM arguments in ForgeGradle auto-generated launch configurations.
Example of broken run configuration:
<?xml version="1.0" encoding="UTF-8"?> <launchConfiguration type="org.eclipse.jdt.launching.localJavaApplication"> <stringAttribute key="org.eclipse.jdt.launching.MAIN_TYPE" value="GradleStart" /> <stringAttribute key="org.eclipse.jdt.launching.PROJECT_ATTR" value="GraphLib" /> <stringAttribute key="org.eclipse.jdt.launching.WORKING_DIRECTORY" value="/Users/NAMEGOESHERE/git/GraphLib/run" /> <stringAttribute key="org.eclipse.jdt.launching.VM_ARGUMENTS" value=" -DFORGE_FORCE_FRAME_RECALC=true" /> </launchConfiguration>
Example of functional run configuration:
<?xml version="1.0" encoding="UTF-8" standalone="no"?> <launchConfiguration type="org.eclipse.jdt.launching.localJavaApplication"> <listAttribute key="org.eclipse.debug.core.MAPPED_RESOURCE_PATHS"> <listEntry value="/Explosives+"/> </listAttribute> <listAttribute key="org.eclipse.debug.core.MAPPED_RESOURCE_TYPES"> <listEntry value="4"/> </listAttribute> <booleanAttribute key="org.eclipse.jdt.launching.ATTR_USE_START_ON_FIRST_THREAD" value="true"/> <stringAttribute key="org.eclipse.jdt.launching.MAIN_TYPE" value="GradleStart"/> <stringAttribute key="org.eclipse.jdt.launching.PROJECT_ATTR" value="Explosives+"/> <stringAttribute key="org.eclipse.jdt.launching.WORKING_DIRECTORY" value="/Users/NAMEGOESHERE/git/Explosives+/run"/> </launchConfiguration>
The failure appears to have something to do with the ASM lib. Changing the default runtime config to not contain this VM argument would likely resolve the bug entirely
Example of crash with Mekanism
Issue can be resolved by removing "-DFORGE_FORCE_FRAME_RECALC=true" from the VM arguments in ForgeGradle auto-generated launch configurations.
Example of broken run configuration:
<?xml version="1.0" encoding="UTF-8"?> <launchConfiguration type="org.eclipse.jdt.launching.localJavaApplication"> <stringAttribute key="org.eclipse.jdt.launching.MAIN_TYPE" value="GradleStart" /> <stringAttribute key="org.eclipse.jdt.launching.PROJECT_ATTR" value="GraphLib" /> <stringAttribute key="org.eclipse.jdt.launching.WORKING_DIRECTORY" value="/Users/NAMEGOESHERE/git/GraphLib/run" /> <stringAttribute key="org.eclipse.jdt.launching.VM_ARGUMENTS" value=" -DFORGE_FORCE_FRAME_RECALC=true" /> </launchConfiguration>Example of functional run configuration:
<?xml version="1.0" encoding="UTF-8" standalone="no"?> <launchConfiguration type="org.eclipse.jdt.launching.localJavaApplication"> <listAttribute key="org.eclipse.debug.core.MAPPED_RESOURCE_PATHS"> <listEntry value="/Explosives+"/> </listAttribute> <listAttribute key="org.eclipse.debug.core.MAPPED_RESOURCE_TYPES"> <listEntry value="4"/> </listAttribute> <booleanAttribute key="org.eclipse.jdt.launching.ATTR_USE_START_ON_FIRST_THREAD" value="true"/> <stringAttribute key="org.eclipse.jdt.launching.MAIN_TYPE" value="GradleStart"/> <stringAttribute key="org.eclipse.jdt.launching.PROJECT_ATTR" value="Explosives+"/> <stringAttribute key="org.eclipse.jdt.launching.WORKING_DIRECTORY" value="/Users/NAMEGOESHERE/git/Explosives+/run"/> </launchConfiguration>The failure appears to have something to do with the ASM lib. Changing the default runtime config to not contain this VM argument would likely resolve the bug entirely