KITFORMA · EDITORIAL GUIDE
Why does cancellation followed by Release cause SemaphoreFullException?
KitForma editorial guide. If waiting was canceled before acquisition, the code owns no semaphore permit to release. An unconditional finally around both waiting and work can over-release.
Step-by-step guidance
If waiting was canceled before acquisition, the code owns no semaphore permit to release. An unconditional finally around both waiting and work can over-release.
Await successful acquisition before entering the try/finally that releases it, or track acquisition explicitly when using timeout-returning overloads. Release exactly once after protected work. Do not catch and ignore SemaphoreFullException; it signals broken accounting.
Test cancellation before acquisition and cancellation during work with another waiter. The outline is
await gate.WaitAsync(token); try { await WorkAsync(token); } finally { gate.Release(); }. A semaphore bounds concurrent access but does not make the protected external operation transactional or durable.Sources and verification
Sources checked:
Scope: This editorial guide is based on the cited sources and tool behavior. A forum question or a query observed for our site does not establish market search volume, low competition, guaranteed rankings or inadequate answers elsewhere.
This starter guide was prepared by KitForma with AI assistance. It is not presented as a real member question or an independent user review. Check the sources and the result with your own file; report corrections in the discussion.