You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Juha Heljoranta (p52mm3x) said:
Might be related but stack traces are very different.
This:
explicitouter
at scala.Predef$.assert(Predef.scala:173)
at scala.tools.nsc.Global.assert(Global.scala:231)
at scala.tools.nsc.transform.Erasure$ErasureTransformer.bridgeDefs(Erasure.scala:903)
and:
patmat
at scala.Predef$.assert(Predef.scala:173)
at scala.tools.nsc.Global.assert(Global.scala:231)
at scala.tools.nsc.transform.Erasure$ErasureTransformer.bridgeDefs(Erasure.scala:903)
java.lang.NullPointerException
at scala.reflect.internal.SymbolTable.afterPhase(SymbolTable.scala:208)
at scala.tools.nsc.Global.afterFlatten(Global.scala:1092)
at scala.tools.nsc.transform.Flatten$$anon$1$$anonfun$1.apply(Flatten.scala:70)
@paulp said:
It's a duplicate. You can obtain a thousand different stack traces from this - they all mean "oops, something is concurrently accessing compiler internals."
Random repl crashes almost immediately after starting.
Crash probability is roughly 5 - 8 %.
In all cases :pa\t\n or :pa\t or :pa\n was entered in rapid fashion, or at least that was the intention.
The text was updated successfully, but these errors were encountered: