java.lang.IndexOutOfBoundsException

Wrong offset: 5329. Should be in range: [0, 2886]

Samebug tips0

There are no available Samebug tips.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web4

  • Stack trace

    • java.lang.IndexOutOfBoundsException: Wrong offset: 5329. Should be in range: [0, 2886] at com.intellij.openapi.editor.impl.LineSet.findLineIndex(LineSet.java:141) at com.intellij.openapi.editor.impl.DocumentImpl.getLineNumber(DocumentImpl.java:919) at com.jetbrains.javascript.debugger.ConsolePrinter.setRepeatCount(ConsolePrinter.kt:110) at com.jetbrains.javascript.debugger.ConsolePrinter.add(ConsolePrinter.kt:95) at com.intellij.chromeConnector.debugger.ChromeDebugProcess$ConsoleMessageManager.doAdd(ChromeDebugProcess.kt:122) at com.intellij.chromeConnector.debugger.ChromeDebugProcess$ConsoleMessageManager.access$doAdd(ChromeDebugProcess.kt:86) at com.intellij.chromeConnector.debugger.ChromeDebugProcess$ConsoleMessageManager$alarm$1.run(ChromeDebugProcess.kt:90) at com.intellij.util.concurrency.QueueProcessor.runSafely(QueueProcessor.java:222) at com.intellij.util.Alarm$Request$1.run(Alarm.java:378) at com.intellij.util.Alarm$Request.run(Alarm.java:389) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at com.intellij.util.concurrency.SchedulingWrapper$MyScheduledFutureTask.run(SchedulingWrapper.java:227) at com.intellij.util.concurrency.BoundedTaskExecutor.runFirstTaskThenPollAndRunRest(BoundedTaskExecutor.java:178) at com.intellij.util.concurrency.BoundedTaskExecutor.access$000(BoundedTaskExecutor.java:40) at com.intellij.util.concurrency.BoundedTaskExecutor$2.run(BoundedTaskExecutor.java:197) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    EricEric
    2 times, last one,
    poroszdporoszd
    2 times, last one,