Errors sometimes not rethrown
See original GitHub issueBeen tracking down this tricky bug that was causing some real-world pain 😢
RxJS version: 5.3.1 & 5.4.3
Code to reproduce:
Runnable version here.
Observable.of(0, Scheduler.async)
.mergeMap(() =>
Observable.combineLatest(Observable.of(0))
)
.subscribe(() => { throw new Error('uh oh'); });
Expected behavior:
Error is re-thrown asynchronously and can be handled by normal uncaught exception means. (window.onerror
, uncaughtException
).
Actual behavior:
Error gets swallowed.
Additional information:
combineLatest
seems to be involved here—if you get rid of it, the example behaves as expected.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:12
- Comments:11 (5 by maintainers)
Top Results From Across the Web
'FATAL: exception not rethrown' errors from NPTL
On shutdown, linux IOCs sometimes abort with a "FATAL: exception not rethrown" error rather than exiting cleanly.
Read more >"exception not rethrown" problem - Google Groups
I'm using Pthreads in a C++ program that uses exceptions. When one thread is cancelled (cancellation state is deferred) by the main
Read more >Don't rethrow `new Error(error)`! - Blog - Mark Larah
This is a problem because valuable stack trace information (and any custom error object attributes) will be thrown away and lost when we...
Read more >FATAL: exception not rethrown Aborted (core dumped) · Issue ...
Adrian, I'm getting a similar error: FATAL: exception not rethrown. Aborted (core dumped). I've opened two webcam streams, and it happens ...
Read more >Rethrowing Errors In JavaScript And Node.js
Ben Nadel looks at how to catch and rethrow errors in JavaScript and Node.js by using the throw() keyword.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
The TC39 observable discussions about errors are super interesting and important but can we keep this particular issue about RxJS 5? The current behavior is inconsistent, surprising, and a real source of pain. 😞
Would anyone happen to know how this is not considered a show-stopper given it’s so easy to reproduce?
https://jsbin.com/ribeyeyolo/edit?html,js,console