Currently, ApplyUpdateReturnAsync treats an ObjectDisposedException to mean that the DocumentContainer has been disposed, and tries to get a new container. But there is another case where the handles underneath disappear (like handle for an array of maps inside the hierarchy of data somewhere), which also leads to throwing of ObjectDisposedException. In this case, the current code does nothing as it just gets the previous container. A fix like the following helps get past this. Please review and fix.
Currently, ApplyUpdateReturnAsync treats an ObjectDisposedException to mean that the DocumentContainer has been disposed, and tries to get a new container. But there is another case where the handles underneath disappear (like handle for an array of maps inside the hierarchy of data somewhere), which also leads to throwing of ObjectDisposedException. In this case, the current code does nothing as it just gets the previous container. A fix like the following helps get past this. Please review and fix.