This was observed when writing integration tests for an application with dht.neo support. It occurs when the app is configured to use the dht.neo.mirror request.
When the integration tests use turtle dht.put to write to the fake DHT, the test suite hangs. If the app is tweaked to use legacy mirror functionality (Listen + periodic GetAll) instead of the neo request, the test suite works fine.
It is not clear at this stage whether this is a problem with how the fake DHT handles neo mirror requests, or whether it is a more general problem with the neo mirror request itself. I'll try to test with an up to date neo-supporting dhtnode instance to verify.