Bug SetSubMesh bounds behavior

According to the documentation, calling mesh.SetSubMesh() recalculates the bounds of the sub mesh by default (unless passing MeshUpdateFlags.DontRecalculateBounds).

This works fine, the descriptor.bounds field is updated. However, mesh.bounds does not seem to. If you do:
Debug.Log(mesh.GetSubMesh(0).bounds.extents);

Correct bounds extents are printed to the console. But if you do:
Debug.Log(mesh.bounds.extents);

the extents are always zero, unless you call mesh.RecalculateBounds(). How come recalculating bounds for a sub mesh does not update the mesh bounds? Really looks like a bug...is this intended behavior? What's the point of recalculating bounds for a sub mesh if we need to recalculate the entire mesh bounds afterwards?

 

Ran into the same issue, but I was passing the DontRecalculateBounds flag while passing in a correct manual calculated bounds. I suppose this makes *some* sense, since you're setting a submesh which may not mean you want to set the 'main' mesh.

Would definitely like the docs to be updated to include this difference, had to also assign the bounds to mesh.bounds.

 

Running into this now. I hope this is getting fixed. It's a huge hit on the performance have to do RecalculateBounds in the main thread.