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
Could it be that the fiber in which a fatal error was thrown just cannot be interrupted? If so then it explains why the shutdown hook blocks indefinitely.
P.S.
For some reason it looks like the code finishes normally when run with sbt (sbt 1.4.9 prints that the program has completed and then just freezes). However, if the compiled jars are invoked directly with java then the program never stops just as I described.
ZIO 1.0.5
openjdk 11.0.10
The text was updated successfully, but these errors were encountered:
It looks like we suspend indefinitely on attempting to interrupt the fiber in the shut down hook. One possibility is to fork the interruption so we don't wait for it. That results in printing the out of memory error and exiting. Looking into why we can't interrupt there.
The following program never stops:
I suppose that JVM just waits for that shutdown hook to finish its work (but it never happens):
zio/core/jvm/src/main/scala/zio/App.scala
Lines 57 to 61 in 2200981
Could it be that the fiber in which a fatal error was thrown just cannot be interrupted? If so then it explains why the shutdown hook blocks indefinitely.
P.S.
For some reason it looks like the code finishes normally when run with sbt (sbt 1.4.9 prints that the program has completed and then just freezes). However, if the compiled jars are invoked directly with
java
then the program never stops just as I described.ZIO 1.0.5
openjdk 11.0.10
The text was updated successfully, but these errors were encountered: