The fix for RT-24566 introduced the internal concept of shared textures that share a common VRAM texture, but have different information in their Java object wrapper (such as the wrap mode that they expect to use).

The code that ensures that the latest pixels have been loaded to a texture from its in-memory representation uses flags in the Texture object to test if the image data is newer than the VRAM pixels, but the flags are not maintained properly between 2 shared textures that point to the same VRAM representation so we can end up with cases where the same image data must be uploaded more than once (i.e. once per shared version of the texture).  This is a minor performance issue since it would only arise in odd circumstances, such as when an image is shared between an ImageView and an ImagePattern and that image is constantly changing.