|author||David Mason <email@example.com>||2019-09-18 13:19:36 -0700|
|committer||Alexander Soldatov/AI Compiler Lab /SRR/Staff Engineer/삼성전자 <firstname.lastname@example.org>||2019-10-07 11:59:33 +0300|
Prevent freeing of the profiler on process shutdown.
Diffstat (limited to 'src/vm/ceemain.cpp')
1 files changed, 6 insertions, 11 deletions
diff --git a/src/vm/ceemain.cpp b/src/vm/ceemain.cpp
index 508693767f..8f2c46fbc5 100644
@@ -1470,16 +1470,14 @@ void STDMETHODCALLTYPE EEShutDownHelper(BOOL fIsDllUnloading)
// callbacks from coming into the profiler even after Shutdown() has been called.
// See https://github.com/dotnet/coreclr/issues/22176 for an example of how that
- // Callbacks will be prevented when ProfilingAPIUtility::Terminate() changes the state
- // to detached, which occurs shortly afterwards. It might be kinder to make the detaching
- // transition before calling Shutdown(), but if we do we'd have to be very careful not
- // to break profilers that were relying on being able to call various APIs during
- // Shutdown(). I suspect this isn't something we'll ever do unless we get complaints.
+ // To prevent issues when profilers are attached we intentionally skip freeing the
+ // profiler here. Since there is no guarantee that the profiler won't be accessed after
+ // we free it (e.g. through callbacks or ELT hooks), we can't safely free the profiler.
- // If EEShutdown is not being called due to a ProcessDetach event, so
- // the profiler should still be present
- if (!g_fProcessDetach)
+ // Don't call back in to the profiler if we are being torn down, it might be unloaded
+ if (!fIsDllUnloading)
@@ -1488,9 +1486,6 @@ void STDMETHODCALLTYPE EEShutDownHelper(BOOL fIsDllUnloading)
g_fEEShutDown |= ShutDown_Profiler;
- // Free the interface objects.
#endif // PROFILING_SUPPORTED