sbt - double free or corruption (!prev) error whenever running mocha tests












1















I've got an sbt project that I run front-end tests on with sbt mocha. Whenever I attempt to do so, I get the below error. Everything else runs properly - I can do sbt test which will run my specs2 scala tests but error out on the mocha tests. I can even run the project itself without issue.



com.typesafe.sbt.jse.SbtJsTask$JsTaskFailure: double free or corruption (!prev)

at com.typesafe.sbt.jse.SbtJsTask$$anonfun$com$typesafe$sbt$jse$SbtJsTask$$executeJsOnEngine$1.apply(SbtJsTask.scala:218)
at com.typesafe.sbt.jse.SbtJsTask$$anonfun$com$typesafe$sbt$jse$SbtJsTask$$executeJsOnEngine$1.apply(SbtJsTask.scala:190)
at scala.util.Success$$anonfun$map$1.apply(Try.scala:206)
at scala.util.Try$.apply(Try.scala:161)
at scala.util.Success.map(Try.scala:206)
at scala.concurrent.Future$$anonfun$map$1.apply(Future.scala:235)
at scala.concurrent.Future$$anonfun$map$1.apply(Future.scala:235)
at scala.concurrent.impl.CallbackRunnable.run(Promise.scala:32)
at scala.concurrent.impl.ExecutionContextImpl$$anon$3.exec(ExecutionContextImpl.scala:107)
at scala.concurrent.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260)
at scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1339)
at scala.concurrent.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979)
at scala.concurrent.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107)
[error] (<projectnameredacted>/*:mochaExecuteTests) com.typesafe.sbt.jse.SbtJsTask$JsTaskFailure: double free or corruption (!prev)`


I've tried doing an sbt clean, I've tried deleting the .ivy2 and .sbt directories, forcing sbt to rebuild itself.



I'm running sbt 0.13.17 and, due to this being a company project, cannot change the sbt version. It's also utilizing scala 2.12.7.



From what I've read, the issue comes from trying to load multiple instances of standard libraries, but the error I'm getting doesn't come from any of the standard libraries, it comes from an sbt package that the project requires and has used without issue for months. Here is where I got that information.










share|improve this question



























    1















    I've got an sbt project that I run front-end tests on with sbt mocha. Whenever I attempt to do so, I get the below error. Everything else runs properly - I can do sbt test which will run my specs2 scala tests but error out on the mocha tests. I can even run the project itself without issue.



    com.typesafe.sbt.jse.SbtJsTask$JsTaskFailure: double free or corruption (!prev)

    at com.typesafe.sbt.jse.SbtJsTask$$anonfun$com$typesafe$sbt$jse$SbtJsTask$$executeJsOnEngine$1.apply(SbtJsTask.scala:218)
    at com.typesafe.sbt.jse.SbtJsTask$$anonfun$com$typesafe$sbt$jse$SbtJsTask$$executeJsOnEngine$1.apply(SbtJsTask.scala:190)
    at scala.util.Success$$anonfun$map$1.apply(Try.scala:206)
    at scala.util.Try$.apply(Try.scala:161)
    at scala.util.Success.map(Try.scala:206)
    at scala.concurrent.Future$$anonfun$map$1.apply(Future.scala:235)
    at scala.concurrent.Future$$anonfun$map$1.apply(Future.scala:235)
    at scala.concurrent.impl.CallbackRunnable.run(Promise.scala:32)
    at scala.concurrent.impl.ExecutionContextImpl$$anon$3.exec(ExecutionContextImpl.scala:107)
    at scala.concurrent.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260)
    at scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1339)
    at scala.concurrent.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979)
    at scala.concurrent.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107)
    [error] (<projectnameredacted>/*:mochaExecuteTests) com.typesafe.sbt.jse.SbtJsTask$JsTaskFailure: double free or corruption (!prev)`


    I've tried doing an sbt clean, I've tried deleting the .ivy2 and .sbt directories, forcing sbt to rebuild itself.



    I'm running sbt 0.13.17 and, due to this being a company project, cannot change the sbt version. It's also utilizing scala 2.12.7.



    From what I've read, the issue comes from trying to load multiple instances of standard libraries, but the error I'm getting doesn't come from any of the standard libraries, it comes from an sbt package that the project requires and has used without issue for months. Here is where I got that information.










    share|improve this question

























      1












      1








      1








      I've got an sbt project that I run front-end tests on with sbt mocha. Whenever I attempt to do so, I get the below error. Everything else runs properly - I can do sbt test which will run my specs2 scala tests but error out on the mocha tests. I can even run the project itself without issue.



      com.typesafe.sbt.jse.SbtJsTask$JsTaskFailure: double free or corruption (!prev)

      at com.typesafe.sbt.jse.SbtJsTask$$anonfun$com$typesafe$sbt$jse$SbtJsTask$$executeJsOnEngine$1.apply(SbtJsTask.scala:218)
      at com.typesafe.sbt.jse.SbtJsTask$$anonfun$com$typesafe$sbt$jse$SbtJsTask$$executeJsOnEngine$1.apply(SbtJsTask.scala:190)
      at scala.util.Success$$anonfun$map$1.apply(Try.scala:206)
      at scala.util.Try$.apply(Try.scala:161)
      at scala.util.Success.map(Try.scala:206)
      at scala.concurrent.Future$$anonfun$map$1.apply(Future.scala:235)
      at scala.concurrent.Future$$anonfun$map$1.apply(Future.scala:235)
      at scala.concurrent.impl.CallbackRunnable.run(Promise.scala:32)
      at scala.concurrent.impl.ExecutionContextImpl$$anon$3.exec(ExecutionContextImpl.scala:107)
      at scala.concurrent.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260)
      at scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1339)
      at scala.concurrent.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979)
      at scala.concurrent.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107)
      [error] (<projectnameredacted>/*:mochaExecuteTests) com.typesafe.sbt.jse.SbtJsTask$JsTaskFailure: double free or corruption (!prev)`


      I've tried doing an sbt clean, I've tried deleting the .ivy2 and .sbt directories, forcing sbt to rebuild itself.



      I'm running sbt 0.13.17 and, due to this being a company project, cannot change the sbt version. It's also utilizing scala 2.12.7.



      From what I've read, the issue comes from trying to load multiple instances of standard libraries, but the error I'm getting doesn't come from any of the standard libraries, it comes from an sbt package that the project requires and has used without issue for months. Here is where I got that information.










      share|improve this question














      I've got an sbt project that I run front-end tests on with sbt mocha. Whenever I attempt to do so, I get the below error. Everything else runs properly - I can do sbt test which will run my specs2 scala tests but error out on the mocha tests. I can even run the project itself without issue.



      com.typesafe.sbt.jse.SbtJsTask$JsTaskFailure: double free or corruption (!prev)

      at com.typesafe.sbt.jse.SbtJsTask$$anonfun$com$typesafe$sbt$jse$SbtJsTask$$executeJsOnEngine$1.apply(SbtJsTask.scala:218)
      at com.typesafe.sbt.jse.SbtJsTask$$anonfun$com$typesafe$sbt$jse$SbtJsTask$$executeJsOnEngine$1.apply(SbtJsTask.scala:190)
      at scala.util.Success$$anonfun$map$1.apply(Try.scala:206)
      at scala.util.Try$.apply(Try.scala:161)
      at scala.util.Success.map(Try.scala:206)
      at scala.concurrent.Future$$anonfun$map$1.apply(Future.scala:235)
      at scala.concurrent.Future$$anonfun$map$1.apply(Future.scala:235)
      at scala.concurrent.impl.CallbackRunnable.run(Promise.scala:32)
      at scala.concurrent.impl.ExecutionContextImpl$$anon$3.exec(ExecutionContextImpl.scala:107)
      at scala.concurrent.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260)
      at scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1339)
      at scala.concurrent.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979)
      at scala.concurrent.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107)
      [error] (<projectnameredacted>/*:mochaExecuteTests) com.typesafe.sbt.jse.SbtJsTask$JsTaskFailure: double free or corruption (!prev)`


      I've tried doing an sbt clean, I've tried deleting the .ivy2 and .sbt directories, forcing sbt to rebuild itself.



      I'm running sbt 0.13.17 and, due to this being a company project, cannot change the sbt version. It's also utilizing scala 2.12.7.



      From what I've read, the issue comes from trying to load multiple instances of standard libraries, but the error I'm getting doesn't come from any of the standard libraries, it comes from an sbt package that the project requires and has used without issue for months. Here is where I got that information.







      scala sbt mocha






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 21 '18 at 21:48









      IanCZaneIanCZane

      12012




      12012
























          1 Answer
          1






          active

          oldest

          votes


















          0














          It ended up being an issue with my version of Node.js. Once I updated from 10.0.0 to 11.2.0 the issue went away.






          share|improve this answer























            Your Answer






            StackExchange.ifUsing("editor", function () {
            StackExchange.using("externalEditor", function () {
            StackExchange.using("snippets", function () {
            StackExchange.snippets.init();
            });
            });
            }, "code-snippets");

            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "1"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53420931%2fsbt-double-free-or-corruption-prev-error-whenever-running-mocha-tests%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            It ended up being an issue with my version of Node.js. Once I updated from 10.0.0 to 11.2.0 the issue went away.






            share|improve this answer




























              0














              It ended up being an issue with my version of Node.js. Once I updated from 10.0.0 to 11.2.0 the issue went away.






              share|improve this answer


























                0












                0








                0







                It ended up being an issue with my version of Node.js. Once I updated from 10.0.0 to 11.2.0 the issue went away.






                share|improve this answer













                It ended up being an issue with my version of Node.js. Once I updated from 10.0.0 to 11.2.0 the issue went away.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 28 '18 at 15:07









                IanCZaneIanCZane

                12012




                12012
































                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Stack Overflow!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53420931%2fsbt-double-free-or-corruption-prev-error-whenever-running-mocha-tests%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    How to change which sound is reproduced for terminal bell?

                    Title Spacing in Bjornstrup Chapter, Removing Chapter Number From Contents

                    Can I use Tabulator js library in my java Spring + Thymeleaf project?