asked Oct 11 '17 at 03:23 by AndyZehner (11)

I get the message "Nektar Impact LX25+ crashed | array index out of range" each time I try and start Bitwig Studio 2. I had been using Butwig 8-track OK, but this new error message is happening all the time since I upgraded.

I have the same problem.. did you ever get around this?

here is the stack trace from the log:

[2018-06-10 14:32:17 notifications error] IMPACT LX25+ crashed: Array index out of range: 53
[2018-06-10 14:32:44 float-gui-widgets error] :
    java.lang.ArrayIndexOutOfBoundsException: Array index out of range: 53
    at jdk.internal.dynalink.beans.BeanLinker.rangeCheck(BeanLinker.java:369)
    at jdk.nashorn.internal.scripts.Script$Recompilation$1951$59389$IMPACT_LX25+_control.Z8112FC4E83E92470E(IMPACT_LX25+.control.js:142)
    at jdk.nashorn.internal.scripts.Script$Recompilation$1948$58100A$IMPACT_LX25+_control.Z811100C303EB1F922(IMPACT_LX25+.control.js:138)
    at jdk.nashorn.internal.scripts.Script$Recompilation$1946$32396A$IMPACT_LX25+_control.Z81137977D3E8A9321(IMPACT_LX25+.control.js:78)
    at jdk.nashorn.internal.scripts.Script$Recompilation$1945$79975$IMPACT_LX25+_control.nektarinit#L:181#L:181(IMPACT_LX25+.control.js:182)
    at jdk.nashorn.internal.runtime.ScriptFunctionData.invoke(ScriptFunctionData.java:637)
    at jdk.nashorn.internal.runtime.ScriptFunction.invoke(ScriptFunction.java:494)
    at jdk.nashorn.internal.runtime.ScriptRuntime.apply(ScriptRuntime.java:393)
    at jdk.nashorn.api.scripting.ScriptObjectMirror.call(ScriptObjectMirror.java:117)
    at com.bitwig.flt.control_surface.proxy.BitwigStudioHost$1.run(SourceFile:695)
    at com.bitwig.flt.control_surface.proxy.BitwigStudioHost$ScheduledTask.invokeCallback(SourceFile:675)
        at fhk.qCA(SourceFile:95)
    at fhk.rEp(SourceFile:91)
    at zwq.YKd(SourceFile:128)
    at GER.Nly(SourceFile:77)
    at YsC.ucN(SourceFile:249)
    at OrX.qCA(SourceFile:241)
    at HXd.YKd(SourceFile:252)
    at ZmX.run(SourceFile:91)
    at HXd.run(SourceFile:106)

I have to say, being a node developer, this is some butt-ugly js, I'm guessing it is machine generated, no human would write code like this..

It looks like it possibly dies in here in the nashorn js runtime,or the BeanLinker java class above it in the stack,:

for (var c = 0; c < Z810D1D0423EF02DA3; c++) 0 < a && !Z811130D833EAE1290(DIRECT_KNOB_GROUP1_MAPPINGS[c]) && (Z811130D833EAE1290(ACTIVE_MAP_OBJECT.Z8114D80893E74928A[Z810D8E0753EE938DF[c]]) && (DIRECT_KNOB_GROUP1_MAPPINGS[c] = ACTIVE_MAP_OBJECT.Z8114D80893E74928A[Z810D8E0753EE938DF[c]]),
        Z811130D833EAE1290(DIRECT_KNOB_GROUP1_MAPPINGS[c]) ? directParamsInUse.push(Z810739DE93F4EB8BB.Z81121ED093EA0D836[DIRECT_KNOB_GROUP1_MAPPINGS[c]]) : (DIRECT_KNOB_GROUP1_MAPPINGS[c] = b.Z8114FAD773E72106A[Z810D8E0753EE938DF[c]], Z811130D833EAE1290(DIRECT_KNOB_GROUP1_MAPPINGS[c]) && directParamsInUse.push(Z810739DE93F4EB8BB.Z81121ED093EA0D836[DIRECT_KNOB_GROUP1_MAPPINGS[c]])));

According to the OpenJDK sources for the nashorn runtime BeanLinker a range check is failing here:

 private static final boolean rangeCheck(final Object array, final Object index) {
        if(!(index instanceof Number)) {
            return false;
        }
        final Number n = (Number)index;
        final int intIndex = n.intValue();
        final double doubleValue = n.doubleValue();
        if(intIndex != doubleValue && !Double.isInfinite(doubleValue)) { // let infinite trigger IOOBE
            return false;
        }
        if(0 <= intIndex && intIndex < Array.getLength(array)) {
            return true;
        }
        throw new ArrayIndexOutOfBoundsException("Array index out of range: " + n);
}

The code about ( line 369 ) is trowing and ArrayIndexOutOfBoundsException, is there some fix I can make to the controller js code to not trip the number parser?

Looks like bad number parsing to me but I gave up Java for sanity long ago..

Any thoughts from the support folks on a fix?

link

answered Jun 10 at 18:58 by ctrauma (11)

edited Jun 10 at 20:56

bump still an issue in 2.4 beta 2

link

answered Aug 16 at 04:27 by ctrauma (11)

edited Aug 16 at 04:28

Opened a ticket with Nektar, they are aware of the issue and working on a fix. I'll post here when I get more info.

link

answered 2 days ago by ctrauma (11)

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

Markdown Basics

  • *italic* or __italic__
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Tags:

×29

Asked: Oct 11 '17 at 03:23

Seen: 405 times

Last updated: 2 days ago