CC @nigeltao @crawshaw

The short answer is, no, it should not work.

A Buffer is essentially an *image.RGBA, but not all *image.RGBAs are valid Buffers. (If they were, the Upload method might as well take an *image.RGBA instead of a Buffer). Drivers may assume that the memory backing a Buffer's pixels are specially allocated, such as shared memory, shared across multiple processes. Arbitrary *image.RGBAs do not satisfy that assumption.

As I tried to say on #14026, your Editor shouldn't have an *image.RGBA or be an *image.RGBA. Instead, it should be able to render itself onto a Buffer's *image.RGBA (where the Buffer is provided by Screen.NewBuffer).

On a side note, with your original code snippet:

*buf.RGBA() = *img
tx.Upload(image.ZP, buf, buf.Bounds())
win.Copy(min, tx, tx.Bounds(), screen.Src, nil)

you might not need to explicitly use a Texture. A Window already has an Upload method, which takes a Buffer.

As I tried to say on #14026, your Editor shouldn't have an *image.RGBA or be an *image.RGBA. Instead, it should be able to render itself onto a Buffer's *image.RGBA (where the Buffer is provided by Screen.NewBuffer).

Ah, thank you. This is obvious now that you say it (I missed it last time, apparently). I've been stuck on the idea that I need to construct my own image, and then copy it to the buffer.

you might not need to explicitly use a Texture. A Window already has an Upload method, which takes a Buffer.

Yes, my example code was simplified. Usually I can reuse the texture (which I believe is hypothetically cheaper than uploading the buffer each time).

CL https://golang.org/cl/19211 mentions this issue.