So I thought I'd update a smidge... The duplicate console msg bug was actually my fault.
I was running the function from my event system. In other words it wasn't part of the procedural chain of function calls. So it took a little bit to notice. But the point is I eventually fixed that as well.
I never did release the code because it doesn't actually work.. well it works but it's not useful without multithreading or modifying the mesh extractor.
On my system it takes about 700ms or approx 3/4 of a second just to extract a 64x64x64 cube, I think I even tried smaller volumes with little improvement. The problem with this is you'd need to separate it into another thread so the rendering isn't affected by the long freeze up.
Many people know this already, have formed their own solutions, and there is little to no information about it easily available.
I've read a bit about moore neighborhoods. I'm kind of confused why extraction doesn't use them. Or polyvox at all for that matter. Care to shed some light on that?