Aha. No, it happens with jemplode 52 also, which means presumably something else caused it. Guess I'll try tcpdump and see what's happening.