Fix BlockHound false positive in stack trace recovery (#2895)

Fixes #2894
Kotlin · Sep 2, 2021 · 6055432 · 6055432
1 parent d3ead6f
commit 6055432
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 0 deletions.
diff --git a/.../jvm/src/internal/ExceptionsConstuctor.kt → ...jvm/src/internal/ExceptionsConstructor.kt b/.../jvm/src/internal/ExceptionsConstuctor.kt → ...jvm/src/internal/ExceptionsConstructor.kt
diff --git a/kotlinx-coroutines-debug/src/CoroutinesBlockHoundIntegration.kt b/kotlinx-coroutines-debug/src/CoroutinesBlockHoundIntegration.kt
@@ -19,6 +19,8 @@ public class CoroutinesBlockHoundIntegration : BlockHoundIntegration {
         allowServiceLoaderInvocationsOnInit()
         allowBlockingCallsInReflectionImpl()
         allowBlockingCallsInDebugProbes()
+        // Stacktrace recovery cache is guarded by lock
+        allowBlockingCallsInside("kotlinx.coroutines.internal.ExceptionsConstructorKt", "tryCopyException")
         /* The predicates that define that BlockHound should only report blocking calls from threads that are part of
         the coroutine thread pool and currently execute a CPU-bound coroutine computation. */
         addDynamicThreadPredicate { isSchedulerWorker(it) }