Correct; this is not a regression, not a showstopper, but a new illustration of an existing bug. We may remove the shm backing store, and destroy the shm object (or let it clean up) but it will attempt to re-remove itself. It's illustrating the bug, no patch was forthcoming, I'm considering it closed until the next go-around with release 1.2.13. といってるじゃないか <www.mail-archive.com/dev@apr.apache.org/msg19314.html>