ReactiveX/RxJava 47055
RxJava – Reactive Extensions for the JVM – a library for composing asynchronous and event-based programs using observable sequences for the Java VM.
ReactiveX/rxjs 28982
A reactive programming library for JavaScript
ReactiveX/RxAndroid 19785
RxJava bindings for Android
ReactiveX/RxGo 4595
Reactive Extensions for the Go language.
ReactiveX/rxdart 3258
The Reactive Extensions for Dart
ReactiveX/RxCpp 2835
Reactive Extensions for C++
ReactiveX/learnrx 1406
A series of interactive exercises for learning Microsoft's Reactive Extensions Library for Javascript.
ReactiveX/IxJS 1247
The Interactive Extensions for JavaScript
RxJava bindings for JavaFX
RxJava bindings for Clojure
startedReactiveX/rxjs
started time in 37 minutes
startedReactiveX/rxdart
started time in 2 hours
PR opened ReactiveX/RxSwift
Add support for using DiffableDataSource with Rx extensions. Fix crash in #2368
pr created time in 2 hours
startedReactiveX/RxGo
started time in 2 hours
startedReactiveX/rxjs
started time in 6 hours
startedReactiveX/rxjs
started time in 7 hours
startedReactiveX/RxCpp
started time in 11 hours
startedReactiveX/RxAndroid
started time in 13 hours
startedReactiveX/RxKotlin
started time in 15 hours
startedReactiveX/rxjs
started time in 16 hours
startedReactiveX/rxjs
started time in 18 hours
issue commentReactiveX/rxjs
Having two `interval` streams running at the same time sometimes causes them to freeze/halt
Maybe it's throttling of timers in chrome.
comment created time in 18 hours
issue openedReactiveX/rxjs
Having two `interval` streams running at the same time sometimes causes them to freeze/halt
Describe the bug
I have two streams created with interval operator:
- "main" which emits every 60 seconds
- "secondary" which emits every 3 seconds
When they run at the same time, sometimes they "freeze" or "halt" and do not emit for some time. It happens randomly, I didn't find one rule by which it occurs.
Expected behavior
The streams created with interval operator should emit according to the time that was set at the beginning.
Reproduction code
No response
Reproduction URL
https://stackblitz.com/edit/stackblitz-starters-6jltsf?file=src%2Fmain.ts
Version
7.8.1
Environment
No response
Additional context
The code in Stackblitz measures time between each emission for two streams: main and secondary. Then compares this time to the one set in interval operator. If the time measured is 1.5x (or more) times greater than original one then report error to the console.
Below you can see two screenshots that I took. They show that it occurs randomly (sometimes there are no errors):
Here you can see that it took 127 emissions for secondary stream to exceed its original interval time (3 seconds) by around 16s and 35s seconds.
Here it happened quite quickly and for both main and secondary.
created time in 18 hours
startedReactiveX/RxJava
started time in 19 hours
startedReactiveX/RxSwift
started time in 21 hours
startedReactiveX/RxGo
started time in 21 hours
startedReactiveX/rxjs
started time in a day
issue commentReactiveX/rxjs-tslint
Is there any solution to this problem.
comment created time in a day
startedReactiveX/rxdart
started time in a day
startedReactiveX/IxJS
started time in a day
startedReactiveX/IxJS
started time in a day
startedReactiveX/RxJava
started time in a day
startedReactiveX/RxJava
started time in a day
startedReactiveX/RxAndroid
started time in a day
startedReactiveX/RxJava
started time in a day
startedReactiveX/RxJava
started time in a day
startedReactiveX/rxjs
started time in a day
startedReactiveX/rxjs
started time in a day
startedReactiveX/RxJava
started time in a day