playframework 2.0 - Why does "sbt run" fail with OutOfMemoryError while "activator run" works fine? -


i can start application activator run simple sbt run ends either outofmemoryerror or sudden termination of application.

exception: java.lang.outofmemoryerror thrown uncaughtexceptionhandler in thread "play-akka.actor.default-dispatcher-2" 

if understanding right activator should delegate commands beside custom one's sbt. apparently, seems activator more.

how can find difference? there mandatory jvm settings should set before running app sbt?

my environment java 7, windows 7 , sbt 0.13.7

fundamentally, there's no difference. activator invokes sbt. little bit more though, includes sbt plugins provide ui , ability create new project templates. invokes sbt more sensible default jvm settings vanilla sbt invoker scripts, including more memory.

how set better defaults depends on sbt invoker script you're using, , may depend on how installed sbt. scripts support sbt_opts environment variable, put -xmx1024m in example give sbt gig of heap space. may want add -xx:maxpermsize=768m if you're getting perm gen space out of memory errors.


Comments

Popular posts from this blog

matlab - "Contour not rendered for non-finite ZData" -

delphi - Indy UDP Read Contents of Adata -

javascript - Any ideas when Firefox is likely to implement lengthAdjust and textLength? -