Scala: Parallel collection in object initializer causes a program to hang

by

This is an inherent problem which can happen in Scala when releasing a reference to the singleton object before the construction is complete. It happens due to a different thread trying to access the object ParCollectionInInitializerTest before it has been fully constructed.
It has nothing to do with the main method, rather, it has to do with initializing the object that contains the main method — try running this in the REPL, typing in the expression ParCollectionInInitializerTest and you’ll get the same results. It also doesn’t have anything to do with fork-join worker threads being daemon threads.

Singleton objects are initialized lazily. Every singleton object can be initialized only once. That means that the first thread that accesses the object (in your case, the main thread) must grab a lock of the object, and then initialize it. Every other thread that comes subsequently must wait for the main thread to initialize the object and eventually release the lock. This is the way singleton objects are implemented in Scala.

In your case the parallel collection worker thread tries accessing the singleton object to invoke doSomething, but cannot do so until the main thread completes initializing the object — so it waits. On the other hand, the main thread waits in the constructor until the parallel operation completes, which is conditional upon all the worker threads completing — the main thread holds the initialization lock for the singleton all the time. Hence, a deadlock occurs.

You can cause this behaviour with futures from 2.10, or with mere threads, as shown below:

def execute(body: =>Unit) {
  val t = new Thread() {
    override def run() {
      body
    }
  }

  t.start()
  t.join()
}

object ParCollection {

  def doSomething() { println("Doing something") }

  execute {
    doSomething()
  }

}

Paste this into the REPL, and then write:

scala> ParCollection

and the REPL hangs.

More Related Contents:

  1. Scala 2.8 breakOut
  2. Is the Scala 2.8 collections library a case of “the longest suicide note in history”? [closed]
  3. Why is Scala’s immutable Set not covariant in its type?
  4. What is the difference between JavaConverters and JavaConversions in Scala?
  5. When should I choose Vector in Scala?
  6. What does param: _* mean in Scala?
  7. Scala 2.8 collections design tutorial
  8. withFilter instead of filter
  9. What type to use to store an in-memory mutable data table in Scala?
  10. Scala Map implementation keeping entries in insertion order?
  11. Stream vs Views vs Iterators
  12. How to read files from resources folder in Scala?
  13. Function returns an empty List in Spark
  14. Scala: Why does Seq.contains take an Any argument, instead of an argument of the sequence type?
  15. Reduce, fold or scan (Left/Right)?
  16. Scala Sets contain the same elements, but sameElements() returns false
  17. Difference between MutableList and ListBuffer
  18. Scala best way of turning a Collection into a Map-by-key?
  19. scala parallel collections degree of parallelism
  20. Combining two lists into one in Scala
  21. Specifying the filename when saving a DataFrame as a CSV [duplicate]
  22. Spark unionAll multiple dataframes
  23. Spark performance for Scala vs Python
  24. How to write spark streaming DF to Kafka topic
  25. sender inside a future
  26. When and why should one use Applicative Functors in Scala
  27. Is there way to create tuple from list(without codegeneration)?
  28. What are Scala continuations and why use them?
  29. Scala variable argument list with call-by-name possible?
  30. Scalaz Bind[Seq] typeclass

Leave a Comment