CarTechnoloGY
[E-sys] 3.33.x 64bit and out of memory (heap size) - Printable Version

+- CarTechnoloGY (https://cartechnology.co.uk)
+-- Forum: Discussions All about Software and Hardware (https://cartechnology.co.uk/forumdisplay.php?fid=310)
+--- Forum: Automotive Help & Discussions / Software and Hardware (https://cartechnology.co.uk/forumdisplay.php?fid=40)
+---- Forum: BMW - Mini - Rolls Royce (https://cartechnology.co.uk/forumdisplay.php?fid=61)
+---- Thread: [E-sys] 3.33.x 64bit and out of memory (heap size) (/showthread.php?tid=54028)



[E-sys] 3.33.x 64bit and out of memory (heap size) - MicRofT - 23-07-2019

Hi,

Today I tried to update my E-sys software to one of 3.33.x 64-bit versions - until now I was using 3.28.1 32-bit. But each time I tried to code BDC_BODY2 (which is quite a big CAFD file) using this new versionĀ I got 'out of memory' errors and info about heap size in java stack trace, regardless of memory setting in Launcher Pro. I tried to disable all kiswb entries expept for the one needed (S15A), but again the same error.

My laptop has 16GB of RAM and Windows 10 x64 so I don't think there is really a problem with RAM memory.

Do You have any hints for me? Or just stay with Esys 3.28.1? wink


Thanks.


RE: [E-sys] 3.33.x 64bit and out of memory (heap size) - Stratofortress - 23-07-2019

Which launcher are you using and does it support 64 bit versions of E-sys?


RE: [E-sys] 3.33.x 64bit and out of memory (heap size) - MicRofT - 23-07-2019

(23-07-2019, 20:28 PM)Stratofortress Wrote:  Which launcher are you using and does it support 64 bit versions of E-sys?

The latest one, 3.4.2 if I remember correctly.


RE: [E-sys] 3.33.x 64bit and out of memory (heap size) - xxiFear - 26-07-2019

I once had that issue. As soon as i opened any bigger CAFD then Esys crashed and couldnt load any windows. Reinstalling Esys did the trick for me.


RE: [E-sys] 3.33.x 64bit and out of memory (heap size) - VroomVroom - 27-07-2019

(23-07-2019, 19:30 PM)MicRofT Wrote:  Hi,

Today I tried to update my E-sys software to one of 3.33.x 64-bit versions - until now I was using 3.28.1 32-bit. But each time I tried to code BDC_BODY2 (which is quite a big CAFD file) using this new versionĀ I got 'out of memory' errors and info about heap size in java stack trace, regardless of memory setting in Launcher Pro. I tried to disable all kiswb entries expept for the one needed (S15A), but again the same error.

My laptop has 16GB of RAM and Windows 10 x64 so I don't think there is really a problem with RAM memory.

Do You have any hints for me? Or just stay with Esys 3.28.1? wink


Thanks.

Hello!
Just edit Esys.bat and change ThreadStackSize from 1024 to 2048
also change Xmx1024m to Xmx2048m
thats all
have a good day