Reactive Rx 2.0 EventLoopScheduler ObjectDisposedException after dispose

Question

I\'m using Rx 2.0\'s EventLoopScheduler to queue up / serialize work. When I need to dispose the scheduler, if there is remaining work, I will receive an unhandled ObjectDis

Answer 1

It's not that there is work remaining (i.e. the scheduler still has things in its queue), it's that you still have Subscriptions outstanding that are trying to add stuff to that queue.

Dispose all of the Subscriptions and then dispose the Scheduler, and it should work correctly