VerifyError when referring to object which refers to itself

[scabug]

in the following scenario, a java.lang.VerifyError is thrown at runtime as soon as you try to reference LimboStage:

abstract sealed class Stage( val transits: Set[ Stage ])
case object IdleStage   extends Stage( Set.empty )
case object LimboStage  extends Stage( Set( IdleStage, LimboStage ))

Exception in thread "main" java.lang.VerifyError: (class: LimboStage$$, method: <init> signature: ()V) Expecting to find object/array on stack
	at Test$$.main(Test.scala:7)
	at Test.main(Test.scala)

[scabug]

Imported From: https://issues.scala-lang.org/browse/SI-3913?orig=1
Reporter: @Sciss
Attachments:

• Test.scala (created on Oct 9, 2010 8:34:24 PM UTC, 262 bytes)
• Test2.scala (created on Oct 9, 2010 8:50:13 PM UTC, 346 bytes)
• Test3.scala (created on Oct 9, 2010 8:53:20 PM UTC, 397 bytes)

[scabug]

@Sciss said:
Reproduces error

[scabug]

@Sciss said:
there is even more craziness. Test2 produces the following output:

idle transits = Set(BusyStage)
busy transits = Set(null)

so there is uninitialized stuff!

[scabug]

@Sciss said:
Another related bug

[scabug]

@Sciss said:
A workaround is in Test3 -- suggesting that the problem has to do with the way the object's constructor is called.

[scabug]

@Sciss said:
Replacing the constructor argument by an abstract method is a workaround

[scabug]

@paulp said:
Hey, I already fixed this once, waaaay back in #473. Not well enough I guess. Let's see if I've learned anything in the 20 months since r17118.

[scabug]

@paulp said:
(In r23222) Better check for objects trying to sneak themselves into the
superconstructor arguments. Closes #3913, no review.

[scabug]

@paulp said:
I'm ignoring the examples involving cycles as covered elsewhere (e.g. #3342.)