Question: Observable stuck in case StackoverflowException thrown inside Task {}, is it expected? about monix HOT 7 OPEN

Yes, this is because StackOverflowError is considered fatal and unrecoverable.

Traditionally, all Errors are considered fatal (as opposed to Exceptions). Scala has a slightly refined definition of what is fatal (see scala.util.control.NonFatal extractor) but StackOverflowError falls into both definitions so Monix will not try to catch and recover from it.

from monix.

OK, but still I expect to fail observable, rather then just silently stuck.
Or I miss understand something?

from monix.

For an Observable to fail on StackOverflowError, it would have to catch it at some point. But fatal errors should never be caught. They should be allowed to crash the process.

Although I remember that at some point NonFatal did not recognize StackOverflowError as fatal so it may be somewhere in a gray area.

from monix.

I am not sure that problem on Observable side, look like Task is never complete with fail or success - no matter.

from monix.

Yes, but Task doesn't catch it for exactly the same reason.

from monix.

OK, so what is way to deal with this issue: improve error handling on Monix side, or always wrapp code inside Task with try-catch, or add timeout to every Task?

from monix.

Do you happen to have any news on this?
Code must throw an exception and not be silently stuck even without logs.

from monix.