The coordinates are huge so you hit numerical issues.
There’s no particular bug with the tube tool, any tools can go wrong when you hit numerical limits (I could improve this particular use case to be more robust though).
What’s more important/interesting is to understand how it happened in the first place (something must has gone wrong pretty early in the process, did you start off with the base sphere or imported a big model?).
To see coordinates you can display Log in Debug menu, then Performance → Scene.
Ideally the bound should be more or less centered and the overall range should be reasonable, let’s say [0.001 - 1000.0].
There’s no easy way to fix that.
Maybe it’s possible in Nomad but it’s a pain to explain, basically you need to scale down everything, recenter everything, and make sure to bake the matrix, primitive needs to be validated as well… (otherwise there’s no baking possible)