Crash java.io.IOException

[mkrn]

Exception java.io.IOException: Broken pipe
at java.lang.reflect.Constructor.newInstance0
at java.lang.reflect.Constructor.newInstance (Constructor.java:343)
at io.ktor.utils.io.ExceptionUtilsJvmKt$createConstructor$$inlined$safeCtor$1.invoke (ExceptionUtilsJvm.kt:103)
at io.ktor.utils.io.ExceptionUtilsJvmKt$createConstructor$$inlined$safeCtor$1.invoke (ExceptionUtilsJvm.kt:90)
at io.ktor.utils.io.ExceptionUtilsJvmKt.tryCopyException (ExceptionUtilsJvm.kt:45)
at io.ktor.utils.io.ByteBufferChannelKt.rethrowClosed (ByteBufferChannel.kt:2404)
at io.ktor.utils.io.ByteBufferChannelKt.access$rethrowClosed (ByteBufferChannel.kt:1)
at io.ktor.utils.io.ByteBufferChannel.setupStateForWrite$ktor_io (ByteBufferChannel.kt:234)
at io.ktor.utils.io.ByteBufferChannel.writeByte$suspendImpl (ByteBufferChannel.kt:2653)
at io.ktor.utils.io.ByteBufferChannel.writeByte (Unknown Source)
at io.ktor.network.tls.RenderKt.writeRecord (Render.kt:17)
at io.ktor.network.tls.TLSClientHandshake$output$1.invokeSuspend (TLSClientHandshake.kt:118)
at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith (ContinuationImpl.kt:33)
at kotlinx.coroutines.DispatchedTask.run (DispatchedTask.kt:99)
at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely (CoroutineScheduler.kt:589)
at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask (CoroutineScheduler.kt:832)
at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker (CoroutineScheduler.kt:720)
at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run (CoroutineScheduler.kt:707)
Caused by java.io.IOException: Broken pipe
at sun.nio.ch.FileDispatcherImpl.write0
at sun.nio.ch.SocketDispatcher.write (SocketDispatcher.java:55)
at sun.nio.ch.IOUtil.writeFromNativeBuffer (IOUtil.java:93)
at sun.nio.ch.IOUtil.write (IOUtil.java:51)
at sun.nio.ch.SocketChannelImpl.write (SocketChannelImpl.java:512)
at io.ktor.network.sockets.CIOWriterKt$attachForWritingDirectImpl$1$1.invokeSuspend (CIOWriter.kt:109)
at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith (ContinuationImpl.kt:33)
at kotlinx.coroutines.DispatchedTaskKt.resume (DispatchedTask.kt:221)
at kotlinx.coroutines.DispatchedTaskKt.resumeUnconfined (DispatchedTask.kt:177)
at kotlinx.coroutines.DispatchedTaskKt.dispatch (DispatchedTask.kt:149)
at kotlinx.coroutines.CancellableContinuationImpl.dispatchResume (CancellableContinuationImpl.kt:470)
at kotlinx.coroutines.CancellableContinuationImpl.resumeImpl$kotlinx_coroutines_core (CancellableContinuationImpl.kt:504)
at kotlinx.coroutines.CancellableContinuationImpl.resumeImpl$kotlinx_coroutines_core$default (CancellableContinuationImpl.kt:493)
at kotlinx.coroutines.CancellableContinuationImpl.resumeWith (CancellableContinuationImpl.kt:359)
at io.ktor.network.selector.SelectorManagerSupport.handleSelectedKey (SelectorManagerSupport.kt:84)
at io.ktor.network.selector.SelectorManagerSupport.handleSelectedKeys (SelectorManagerSupport.kt:65)
at io.ktor.network.selector.ActorSelectorManager.process (ActorSelectorManager.kt:70)
at io.ktor.network.selector.ActorSelectorManager.access$process (ActorSelectorManager.kt:18)
at io.ktor.network.selector.ActorSelectorManager$process$1.invokeSuspend (Unknown Source:14)
at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith (ContinuationImpl.kt:33)
at kotlinx.coroutines.DispatchedTask.run (DispatchedTask.kt:101)
at kotlinx.coroutines.internal.LimitedDispatcher$Worker.run (LimitedDispatcher.kt:113)
at kotlinx.coroutines.scheduling.TaskImpl.run (Tasks.kt:89)
at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely (CoroutineScheduler.kt:589)
at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask (CoroutineScheduler.kt:823)

[pedroSG94]

Hello,

Which library version are you using?

Also, you can try use java.io sockets instead of ktor socket with:

getStreamClient().setSocketType(SocketType.JAVA)

[mkrn]

Hello thanks for answer. Latest version, yes added socket Type, can this crash still happen with JAVA socket?

[pedroSG94]

Hello,

Hello thanks for answer. Latest version, yes added socket Type, can this crash still happen with JAVA socket?

No, it doesn't should. That method replace ktor socket to java.io sockets.

Are you calling that method before startStream method?
If you call that method after startStream method, it is ignored because the socket is already created.

The problem with that error is that it is internal and I can't catch it. Possible solutions:

• I can try update to last version of ktor but in my experience I had more problems (crashes) using ktor 3.x.x than the current version
• I can select java.io sockets as default socket

[mkrn]

Update from another reproduction pass: we reproduced the same class of RTMPS/Ktor crash on Android by streaming to an rtmps:// endpoint and disabling Wi-Fi mid-stream. The app process died from Ktor TLS close/write handling:

io.ktor.utils.io.ClosedWriteChannelException: Broken pipe
  at io.ktor.utils.io.ByteChannel.getWriteBuffer(ByteChannel.kt:54)
  at io.ktor.utils.io.ByteWriteChannelOperationsKt.writeByte(ByteWriteChannelOperations.kt:19)
  at io.ktor.network.tls.RenderKt.writeRecord(Render.kt:18)
  at io.ktor.network.tls.TLSClientHandshake...
Suppressed: [CoroutineName(cio-tls-closer), ... Dispatchers.IO]
Caused by: java.io.IOException: Broken pipe
  at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:512)
  at io.ktor.network.sockets.CIOWriterKt...

Switching RTMP to SocketType.JAVA before startStream() fixed the fatal crash in our device tests. Wi-Fi off/on and Wi-Fi/mobile/Wi-Fi transitions both recovered without process death and continued sending audio/video packets.

I opened a narrow PR to make Java the default RTMP socket while keeping Ktor opt-in: #2100