Andreas Woess

@tporeba JS does not have a `long` type, so `9007199254740992` will be interpreted as a `double` value. Once the double value is outside the "safe" range, the conversion to long...

In the upcoming GraalVM 22.3, the language classes should now always be found and successfully loaded regardless of the current context class loader, as long as the `org.graalvm.polyglot.*` classes are...

I believe we've fixed this in the upcoming GraalVM 22.3. Can you please try a recent [developer build](https://github.com/graalvm/graalvm-ce-dev-builds/releases) to see if the problem is resolved in that version?

> as this needs to parse general all function arrguments and all object assignments what would be the related files should i create new files or should i implement that...

@frank-dspeed Yes, I mean a context option. Those are defined in the class `JSContextOptions` and `JSParserOptions`. You can follow the examples there.

We have two execution modes, "native" (default) and "JVM" (see https://www.graalvm.org/docs/reference-manual/languages/js/ for more information). Setting jvm options switches to the JVM. Currently, fibonacci is significantly faster in native mode, try...

So, if I understand correctly the `allocations` array is leaked via the JS objects in the `PolyglotException`'s stack trace that you're getting for an `OutOfMemoryError`. I'm afraid this somewhat by...

> Umm, Is this the same Nashorn limit? @moayman Yes, that's is the file size limit for _parsing_ in both engines. Also note that Nashorn automatically splits large JS functions...

@moayman If you eval e.g.: ``` function func1() { /* code */ } function func2() { /* code */ } ``` You should be able to access the functions via...

How do you end up with 350MB of JS? Is it really all code or does it include a large amount of data? Either way, I'd suggest to split it...