Nick Craig-Wood b5cbb7520d lib/pool: fix unreliable TestPoolMaxBufferMemory test ...

This turned out to be a problem in the tests. The tests used to do

1. allocate
2. increment
3. free
4. decrement

But if one goroutine had just completed 2 and another had just
completed 3 then this can cause the test to register too many
allocations.

This was fixed by doing the test in this order instead:

1. allocate
2. increment
3. decrement
4. free

The 4 operations are atomic.

Fixes #8813

2025-09-12 10:39:32 +01:00

..

pool_test.go

lib/pool: fix unreliable TestPoolMaxBufferMemory test

2025-09-12 10:39:32 +01:00

pool.go

pool: fix deadlock with --max-buffer-memory

2025-08-14 16:14:59 +01:00

reader_writer_test.go

build: modernize Go usage

2025-02-28 11:31:14 +00:00

reader_writer.go

pool: fix deadlock with --max-buffer-memory

2025-08-14 16:14:59 +01:00