The ReaderWriterLockSlim introduced in line 21 holds native kernel synchronization objects (especially on Windows) but is never disposed. While the class comment says Disposing is not required, the Dispose() method only calls Finish() which disposes _idleTimer but not _finishLock. In high-throughput scenarios with many short-lived transactions, this could lead to gradual handle exhaustion.

When discarding a child span due to the span limit, the debug log message at line 340 logs SpanId (the transaction's SpanId) instead of span.SpanId (the child span being discarded). This causes misleading debug output that references the wrong span, making troubleshooting more difficult.

Also found at:

• src/Sentry/TransactionTracer.cs:349