Comments (4)
akarnokd
commented on June 2, 2024
1
Yes, that can happen because the new thread worker has to be shut down in some way to not leak it. Operators cancel eagerly and thus this interrupt via shutdownNow can happen while still being on the same thread.
Could you use a different scheduler instead, such as IO or from with a custom executor? Those would not shutdownNow like the vanilla newThread.
from rxjava.
joshallenit
commented on June 2, 2024
Thanks for the tip! Using Schedulers.from(executor) directly avoids this issue. We are using executor.asCoroutineDispatcher().asScheduler() so that we can share threads between coroutines and Rx using limitedParallelism. That leads to this interrupted issue, from a different mechanism then shutdownNow.
at xxx.RxIoThread.interrupt(MonotonicThreadFactory.kt:25)
at kotlinx.coroutines.ThreadState.invoke(Interruptible.kt:145)
at kotlinx.coroutines.ThreadState.invoke(Interruptible.kt:62)
at kotlinx.coroutines.InvokeOnCancelling.invoke(JobSupport.kt:1428)
at kotlinx.coroutines.JobSupport.notifyCancelling(JobSupport.kt:1473)
at kotlinx.coroutines.JobSupport.tryMakeCancelling(JobSupport.kt:796)
at kotlinx.coroutines.JobSupport.makeCancelling(JobSupport.kt:756)
at kotlinx.coroutines.JobSupport.cancelImpl$kotlinx_coroutines_core(JobSupport.kt:672)
at kotlinx.coroutines.JobSupport.parentCancelled(JobSupport.kt:638)
at kotlinx.coroutines.ChildHandleNode.invoke(JobSupport.kt:1436)
at kotlinx.coroutines.JobSupport.notifyCancelling(JobSupport.kt:1473)
at kotlinx.coroutines.JobSupport.tryMakeCancelling(JobSupport.kt:796)
at kotlinx.coroutines.JobSupport.makeCancelling(JobSupport.kt:756)
at kotlinx.coroutines.JobSupport.cancelImpl$kotlinx_coroutines_core(JobSupport.kt:672)
at kotlinx.coroutines.JobSupport.parentCancelled(JobSupport.kt:638)
at kotlinx.coroutines.ChildHandleNode.invoke(JobSupport.kt:1436)
at kotlinx.coroutines.JobSupport.notifyCancelling(JobSupport.kt:1473)
at kotlinx.coroutines.JobSupport.tryMakeCompletingSlowPath(JobSupport.kt:901)
at kotlinx.coroutines.JobSupport.tryMakeCompleting(JobSupport.kt:864)
at kotlinx.coroutines.JobSupport.cancelMakeCompleting(JobSupport.kt:697)
at kotlinx.coroutines.JobSupport.cancelImpl$kotlinx_coroutines_core(JobSupport.kt:668)
at kotlinx.coroutines.JobSupport.cancelInternal(JobSupport.kt:633)
at kotlinx.coroutines.JobSupport.cancel(JobSupport.kt:618)
at kotlinx.coroutines.Job$DefaultImpls.cancel$default(Job.kt:195)
at kotlinx.coroutines.rx3.DispatcherScheduler$DispatcherWorker.dispose(RxScheduler.kt:92)
at io.reactivex.rxjava3.internal.operators.flowable.FlowableSubscribeOn$SubscribeOnSubscriber.cancel(FlowableSubscribeOn.java:142)
from rxjava.
akarnokd
commented on June 2, 2024
Oh, that's a hefty kotlinx stacktrace.
I don't know what and why they do it that way. It's out of control of Rx as we only issue a dispose to the worker.
from rxjava.
joshallenit
commented on June 2, 2024
Okay, closing this then, thanks for the help!
from rxjava.
Related Issues (20)
- v3.1.4: race condition in DeferredScalarSubscription HOT 4
- v3: The marble diagram for cast is incredibly misleading.
- No Development on RxKotlin HOT 5
- missing PNG files in the documentation HOT 1
- 3.x: Items dropped by observeOn without backpressure errors HOT 2
- Consumer buffer of flowable leaks memory HOT 3
- UndeliverableException when use zip compose 2 observable , send Exceptions at same time in the two Observable 。 HOT 3
- 2.x: Infinity loop on subscription cancel HOT 6
- Weird Flowable behavior when flatMapCompletable is being executed in a different thread HOT 2
- Adopt the Scorecard Action to monitor the project's security posture
- DeferredScalarDisposable throws NullPointerException HOT 2
- `3.x` In README.md, add a link to the mentioned JavaFX Scheduler HOT 2
- Broken link in docs/Getting-Started.md
- Marble diagram for `Observable.concatMapMaybe` is wrong HOT 8
- repeatWhen terminate HOT 3
- What does it mean due to lack of requests in MissingBackpressureException HOT 2
- FlowableObserveOn.BaseObserveOnSubscriber will ignore the next datas when cosumer throw exception HOT 3
- io.reactivex.rxjava3.exceptions.UndeliverableException: The exception could not be delivered to the consumer because it has already canceled/disposed the flow or the exception has nowhere to go to begin with HOT 1
- Some Schedulers along with lockingGet will make the application hang HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from rxjava.