Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Repl crashes when trying to enter paste mode rapidly #6510

Closed
scabug opened this issue Oct 10, 2012 · 4 comments
Closed

Repl crashes when trying to enter paste mode rapidly #6510

scabug opened this issue Oct 10, 2012 · 4 comments
Assignees

Comments

@scabug
Copy link

scabug commented Oct 10, 2012

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.

@scabug
Copy link
Author

scabug commented Oct 10, 2012

Imported From: https://issues.scala-lang.org/browse/SI-6510?orig=1
Reporter: Juha Heljoranta (p52mm3x)
Affected Versions: 2.10.0-M7
Duplicates #6299
Attachments:

@scabug
Copy link
Author

scabug commented Oct 10, 2012

@gkossakowski said:
Juha, is this duplicate of SI-6299?

@scabug
Copy link
Author

scabug commented Oct 11, 2012

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)

#6299 has:

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)

@scabug
Copy link
Author

scabug commented May 12, 2013

@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."

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants