Jump to content
Excelsior Forums
Sign in to follow this  
kornelio

Fatal error in Excelsior 6.5

Recommended Posts

Hi,

for some extrange reason, I have successfully compiled our Eclipse RCP with Excelsior 6.5 beta, 2 times at least, and now I can't get to do it :( If I recall correctly, I used all default options, and changed some minor things.

Anyway, all compilations of my RCP end up in this message:

Fatal Error (3): Insuficient Memory

This happens at the very end of the compilation process. After everything is compiled, a message is shown indicating that everything went fine (in fact, no compilation errors), but the build script takes some time before ending (the last copyright message is shown), probably writting the output compiled executable file. It's then when the error comes up. Unfortunately, this happens before the log is written, too...

Our compilation is taking more than 10 hours, and compiling quite a lot of classes (can't recall the number now, sorry, the windows batch file windows closes inmediately after finishing, I'll try executing it from prompt to avoid it being closed)

I have 2Gb memory. Should I get more? Before finishing, the jet.exe process was taking more than 1Gb of RAM.

Any thoughts on this?

Share this post


Link to post
Share on other sites

zztop,

I'll send the prj file ASAP.

More information:

The error seems to happen during link phase. This is the message I get:

files: 61831  errors: 0  warnings: 0  notices: 0

61 methods were compiled with a lower optimization level

due to their very large sizes. These methods' names are logged in kdm-workbench-

native.vaz

with the "LONGLONGTIME:" prefix.

Your project has been successfully compiled.

Note however that 833 methods were compiled with a lower optimization level,

most probably due to obfuscated bytecode.

We would appreciate if you could e-mail the file kdm-workbench-native.vaz

and the .class files listed in it to us at java@excelsior-usa.com. By doing so,

you would help us improve the quality of our product. Thank you!

For more details, see JET User's Guide (Chapter "Application considerations",

Section "Baseline compilation").

XDS Link Version 2.11.19 Copyright © Excelsior 1995-2008.

Fatal error (3): Insufficient memory

external command fault 255:

xlink @"kdm-workbench-native_jetpdb/kdm-workbench-native.rsp"

Link time 5:00.49

Total compilation time 715278:28.14

Share this post


Link to post
Share on other sites

Thank you for this additional information.

The error seems to happen during link phase.

I knew that.  B)

61 methods were compiled with a lower optimization level

due to their very large sizes. These methods' names are logged in kdm-workbench-

native.vaz with the "LONGLONGTIME:" prefix.

That's clear. Most probably, these classes are generated automatically.

Please send us both the project file and kdm-workbench-native.vaz and we will be back to you with a simple workaround. I guess it will significantly reduce the compilation time.

Share this post


Link to post
Share on other sites

zztop,

thanks for the feedback!

I've already sent those two files. Looking forward for that solution!

I just wonder, why the first 2 times it did work and now it doesn't! I guess I've overlooked something in the configuration.

Thanks again!

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×