Eclipse crashes

Edit Subject

http://dl.dropbox.com/u/14767221/6.7z to the recorded program. Could it be due to memory? However I had crashes them with -Xms800m, 100m, 1200m, 2000m. Eclipse process itself does not terminates it just looses eclipse window.

Could you send the .log file contained in the /.metadata folder to support@chrononsystems.com

sent

>Hi Misha,

>So we were able to unpack the recording and open it successfully here.

>I think what you should do is use the 'standalone unpacker.jar' to unpack your recordings.

>http://chronon.onconfluence.com/displ...

>The unpacked recording size in this case was 692MB.

>For these large recordings, we do recommend using the standalone unpacker:

Is problem with eclipse chronon debugger called by corrupted unpacked recording?

no the recording is fine.
we tried unpacking it here and it worked fine.

It seems you are settting an -Xms value for Eclipse but what is the -Xmx value?

We recommended the standalone unpacker since that is the best way to unpack the recording, controlling the exact jvm parameter and see the unpack progress.

Oh, I have mixed up -Xms with -Xmx, I used -Xmx, not -Xms.

What about unpacked with eclipse recording, could it have some broken parts? I could upload it somewhere to check.
I will try to unpack it with stand alone unpacker, but I don't see how that will help, if my unpacked recording has no damages.

the eclipse unpacker uses the exact same jar as the standalone one.
if you use the standalone unpacker then you dont have to give eclipse any extra memory.

for a recording this large we recommend setting the xms value same as xmx and using a value >= 2.5gb. also you should configure the unpacker threads by going to window preferences.

again with the standalone unpacker you can do all this on the command line instead of fiddling with eclipse. the end result in either case would be the same.