Don't re-throw exceptions from default FiberManager exception handler

Summary: It's very unlikely that caller will handle such exceptions and FiberManager can proceed even if one task failed. DFATAL will ensure we still fail on such exceptions in debug builds.

Reviewed By: yfeldblum

Differential Revision: D3273573

fb-gh-sync-id: 55eba19c16429a3c89a2fdf5363fd4b55b3998a2
fbshipit-source-id: 55eba19c16429a3c89a2fdf5363fd4b55b3998a2

diff --git a/folly/experimental/fibers/FiberManager-inl.h b/folly/experimental/fibers/FiberManager-inl.h
index 1e91a5a6b7dc5912aec630a4b811e26e3901c090..52c283f58ef303d166b768975444f0c082809af6 100644 (file)
--- a/folly/experimental/fibers/FiberManager-inl.h
+++ b/folly/experimental/fibers/FiberManager-inl.h
@@ -527,11 +527,9 @@ FiberManager::FiberManager(
           LOG(DFATAL) << "Exception " << typeid(e).name() << " with message '"
                       << e.what() << "' was thrown in "
                       << "FiberManager with context '" << context << "'";
-          throw;
         } catch (...) {
           LOG(DFATAL) << "Unknown exception was thrown in FiberManager with "
                       << "context '" << context << "'";
-          throw;
         }
       }),
       timeoutManager_(std::make_shared<TimeoutController>(*loopController_)),