avoid fmt.Errorf calls for an error that is never read (reduce useless memory allocs)

[sduchesneau]

While chasing memory allocations (heavy usage of WASM modules, leading to thrashing golang garbage collector ...),
I found a lot of fmt.Errorf() called, without any error resurfacing.

The content of these errors are always ignored, so it makes more sense to reuse the same error object, saving a lot of object memory allocations.

[mathetake]

mind sharing how this could be a memory pressure bottleneck in practice?