R redbeardrob Member Licensed User Longtime User Feb 28, 2015 #1 How do you fix heap space errors in version 2.71 running on Windows 7 Pro? I cannot locate the "ini" file discussed in previous threads to edit the dexer. I have already increased the allotted memory for Java itself. B4a will only switch to the Standard dexer one out of 100 times, which has stalled progress completely on my project: Compile Error log below: Parsing code. 2.68 Compiling code. 2.33 Compiling layouts code. 0.00 Generating R file. 0.99 Compiling generated Java code. 3.22 Convert byte code - optimized dex. Error UNEXPECTED TOP-LEVEL ERROR: java.lang.OutOfMemoryError: Java heap space at com.android.dx.util.IntList.<init>(IntList.java:87) at com.android.dx.util.IntList.mutableCopy(IntList.java:345) at com.android.dx.util.LabeledList.<init>(LabeledList.java:45) at com.android.dx.rop.code.BasicBlockList.<init>(BasicBlockList.java:53) at com.android.dx.rop.code.BasicBlockList.getMutableCopy(BasicBlockList.java:216) at com.android.dx.ssa.back.IdenticalBlockCombiner.<init>(IdenticalBlockCombiner.java:50) at com.android.dx.ssa.back.SsaToRop.convert(SsaToRop.java:126) at com.android.dx.ssa.back.SsaToRop.convertToRopMethod(SsaToRop.java:70) at com.android.dx.ssa.Optimizer.optimize(Optimizer.java:102) at com.android.dx.ssa.Optimizer.optimize(Optimizer.java:73) at com.android.dx.dex.cf.CfTranslator.processMethods(CfTranslator.java:273) at com.android.dx.dex.cf.CfTranslator.translate0(CfTranslator.java:134) at com.android.dx.dex.cf.CfTranslator.translate(CfTranslator.java:87) at com.android.dx.command.dexer.Main.processClass(Main.java:487) at com.android.dx.command.dexer.Main.processFileBytes(Main.java:459) at com.android.dx.command.dexer.Main.access$400(Main.java:67) at com.android.dx.command.dexer.Main$1.processFileBytes(Main.java:398) at com.android.dx.cf.direct.ClassPathOpener.processOne(ClassPathOpener.java:135) at com.android.dx.cf.direct.ClassPathOpener.processDirectory(ClassPathOpener.java:191) at com.android.dx.cf.direct.ClassPathOpener.processOne(ClassPathOpener.java:123) at com.android.dx.cf.direct.ClassPathOpener.processDirectory(ClassPathOpener.java:191) at com.android.dx.cf.direct.ClassPathOpener.processOne(ClassPathOpener.java:123) at com.android.dx.cf.direct.ClassPathOpener.processDirectory(ClassPathOpener.java:191) at com.android.dx.cf.direct.ClassPathOpener.processOne(ClassPathOpener.java:123) at com.android.dx.cf.direct.ClassPathOpener.process(ClassPathOpener.java:109) at com.android.dx.command.dexer.Main.processOne(Main.java:422) at com.android.dx.command.dexer.Main.processAllFiles(Main.java:333) at com.android.dx.command.dexer.Main.run(Main.java:209) at com.android.dx.command.dexer.Main.main(Main.java:174) at com.android.dx.command.Main.main(Main.java:91) Optimized dexer failed. Switching to Standard dexer.
How do you fix heap space errors in version 2.71 running on Windows 7 Pro? I cannot locate the "ini" file discussed in previous threads to edit the dexer. I have already increased the allotted memory for Java itself. B4a will only switch to the Standard dexer one out of 100 times, which has stalled progress completely on my project: Compile Error log below: Parsing code. 2.68 Compiling code. 2.33 Compiling layouts code. 0.00 Generating R file. 0.99 Compiling generated Java code. 3.22 Convert byte code - optimized dex. Error UNEXPECTED TOP-LEVEL ERROR: java.lang.OutOfMemoryError: Java heap space at com.android.dx.util.IntList.<init>(IntList.java:87) at com.android.dx.util.IntList.mutableCopy(IntList.java:345) at com.android.dx.util.LabeledList.<init>(LabeledList.java:45) at com.android.dx.rop.code.BasicBlockList.<init>(BasicBlockList.java:53) at com.android.dx.rop.code.BasicBlockList.getMutableCopy(BasicBlockList.java:216) at com.android.dx.ssa.back.IdenticalBlockCombiner.<init>(IdenticalBlockCombiner.java:50) at com.android.dx.ssa.back.SsaToRop.convert(SsaToRop.java:126) at com.android.dx.ssa.back.SsaToRop.convertToRopMethod(SsaToRop.java:70) at com.android.dx.ssa.Optimizer.optimize(Optimizer.java:102) at com.android.dx.ssa.Optimizer.optimize(Optimizer.java:73) at com.android.dx.dex.cf.CfTranslator.processMethods(CfTranslator.java:273) at com.android.dx.dex.cf.CfTranslator.translate0(CfTranslator.java:134) at com.android.dx.dex.cf.CfTranslator.translate(CfTranslator.java:87) at com.android.dx.command.dexer.Main.processClass(Main.java:487) at com.android.dx.command.dexer.Main.processFileBytes(Main.java:459) at com.android.dx.command.dexer.Main.access$400(Main.java:67) at com.android.dx.command.dexer.Main$1.processFileBytes(Main.java:398) at com.android.dx.cf.direct.ClassPathOpener.processOne(ClassPathOpener.java:135) at com.android.dx.cf.direct.ClassPathOpener.processDirectory(ClassPathOpener.java:191) at com.android.dx.cf.direct.ClassPathOpener.processOne(ClassPathOpener.java:123) at com.android.dx.cf.direct.ClassPathOpener.processDirectory(ClassPathOpener.java:191) at com.android.dx.cf.direct.ClassPathOpener.processOne(ClassPathOpener.java:123) at com.android.dx.cf.direct.ClassPathOpener.processDirectory(ClassPathOpener.java:191) at com.android.dx.cf.direct.ClassPathOpener.processOne(ClassPathOpener.java:123) at com.android.dx.cf.direct.ClassPathOpener.process(ClassPathOpener.java:109) at com.android.dx.command.dexer.Main.processOne(Main.java:422) at com.android.dx.command.dexer.Main.processAllFiles(Main.java:333) at com.android.dx.command.dexer.Main.run(Main.java:209) at com.android.dx.command.dexer.Main.main(Main.java:174) at com.android.dx.command.Main.main(Main.java:91) Optimized dexer failed. Switching to Standard dexer.
Erel B4X founder Staff member Licensed User Longtime User Mar 1, 2015 #2 You need to edit the ini file and increase MaxRamForDex value: https://www.b4x.com/android/forum/threads/optimized-hex-out-of-memory-error.41917/#post-252722 Upvote 0
You need to edit the ini file and increase MaxRamForDex value: https://www.b4x.com/android/forum/threads/optimized-hex-out-of-memory-error.41917/#post-252722
R redbeardrob Member Licensed User Longtime User Mar 1, 2015 #3 THANK YOU SO MUCH!!! That link pointed me to manually typing the file path in the browser to find the file, which was the step that had kept the ini file hidden from me. Upvote 0
THANK YOU SO MUCH!!! That link pointed me to manually typing the file path in the browser to find the file, which was the step that had kept the ini file hidden from me.