Issues

With two or more producers, a thread's InvokeAsync(A) can run before its own earlier TryBeginInvoke(B): BoundedMpscQueue.TryDequeue reports a claimed-but-unpublished slot as "empty"

ktsu-dev/Invoker#94 · opened

on Nov 1, 2026

1

Synchronous Invoke() from thread-pool callers takes seconds, or hangs under a capped pool, after the owner has already run the delegate: each return waits for a free pool thread

ktsu-dev/Invoker#91 · opened

on Nov 1, 2026

1

A nested DoInvokes() can't run the item the outer pump has already dequeued, so "pump until the worker finishes" hangs (regression from #80 / f81899e)

ktsu-dev/Invoker#85 · opened

on Oct 29, 2026

1

TryBeginInvoke(B) then InvokeAsync(A) from one thread can run A before B: DoInvokes' per-queue budgets are read at two different moments

ktsu-dev/Invoker#83 · opened

on Oct 19, 2026

1

Invoke delegates run on a thread-pool thread when DoInvokes is pumped with little stack left, because RunSynchronously(TaskScheduler.Default) doesn't always inline

ktsu-dev/Invoker#77 · opened

on Oct 7, 2026

1

Invoker.Demo hangs forever: after `await Task.Run(DoInvokes)`, Main resumes on a pool thread and its next Invoke() waits on a pump nobody calls

ktsu-dev/Invoker#69 · opened

on Oct 5, 2026

1

Invoke/InvokeAsync callers hang forever once the owner loop stops pumping: no cancellation, timeout or shutdown to release them

ktsu-dev/Invoker#63 · opened

on Sep 28, 2026

1

Navigation Menu

Repository navigation

Issues

With two or more producers, a thread's InvokeAsync(A) can run before its own earlier TryBeginInvoke(B): BoundedMpscQueue.TryDequeue reports a claimed-but-unpublished slot as "empty"

Synchronous Invoke() from thread-pool callers takes seconds, or hangs under a capped pool, after the owner has already run the delegate: each return waits for a free pool thread

A nested DoInvokes() can't run the item the outer pump has already dequeued, so "pump until the worker finishes" hangs (regression from #80 / f81899e)

TryBeginInvoke(B) then InvokeAsync(A) from one thread can run A before B: DoInvokes' per-queue budgets are read at two different moments

Invoke delegates run on a thread-pool thread when DoInvokes is pumped with little stack left, because RunSynchronously(TaskScheduler.Default) doesn't always inline

Invoker.Demo hangs forever: after `await Task.Run(DoInvokes)`, Main resumes on a pool thread and its next Invoke() waits on a pump nobody calls

Invoke/InvokeAsync callers hang forever once the owner loop stops pumping: no cancellation, timeout or shutdown to release them

Issues

Issues

Issues

With two or more producers, a thread's InvokeAsync(A) can run before its own earlier TryBeginInvoke(B): BoundedMpscQueue.TryDequeue reports a claimed-but-unpublished slot as "empty"

Synchronous Invoke() from thread-pool callers takes seconds, or hangs under a capped pool, after the owner has already run the delegate: each return waits for a free pool thread

A nested DoInvokes() can't run the item the outer pump has already dequeued, so "pump until the worker finishes" hangs (regression from #80 / f81899e)

TryBeginInvoke(B) then InvokeAsync(A) from one thread can run A before B: DoInvokes' per-queue budgets are read at two different moments

Invoke delegates run on a thread-pool thread when DoInvokes is pumped with little stack left, because RunSynchronously(TaskScheduler.Default) doesn't always inline

Invoker.Demo hangs forever: after await Task.Run(DoInvokes), Main resumes on a pool thread and its next Invoke() waits on a pump nobody calls

Invoke/InvokeAsync callers hang forever once the owner loop stops pumping: no cancellation, timeout or shutdown to release them

Invoker.Demo hangs forever: after `await Task.Run(DoInvokes)`, Main resumes on a pool thread and its next Invoke() waits on a pump nobody calls