Fix BlazePool shut down bug with explicitly expired objects

chrisvest / stormpot

A fast object pool for the JVM

http://chrisvest.github.io/stormpot/

Apache License 2.0

357 stars 42 forks source link

Fix BlazePool shut down bug with explicitly expired objects #136

Closed chrisvest closed 4 years ago

chrisvest commented 4 years ago

This fixes a bug where explicitly expired objects were not deallocated in shut down were not deallocated. The reason was that the explicit expiration appeared as a failed allocation poison to that code path. It is now handled correctly.

Fixes #135