Using get after using set with out calling updatePixels causes an error that seems to be altered in an unhelpful way.

See [this](https://www.khanacademy.org/computer-programming/what-is-e-and-why-is-it-undefined/3141868561?qa_expand_key=kaencrypted_c4a3bfcaa418432eaec9310c697f2087_3ad2326fde28d6dc9914713e1134b7be62d94e931defcb2cafb431653cedf6d0d799a300125a574510e95247e85325a2bf38cb103feb45c617050eafb5f85990c229b9f18a06ddc39a9b0aff3bcb061a3eb0f9422d2e6bd73b5f4ba2918e1210f6aba074af128265d8ea3af4ced229d4c0b0c628cde02e72f4d068c1c64ef4f9d9853adf596226a3476ac9ea9daa0137825a98c25390563e1d8be7a23bd3f7e1l)
help request for more details.
I think I've seen seemingly random/unhelpful e's in other errors, I'll have to look around for more.

Start with the linked reproduction and trace the interaction between get, set, and updatePixels to identify where the error is altered. Then compare the other seemingly random or unhelpful errors mentioned in the issue; the work is done when the reported case produces a useful, accurate error.

Written by the indexing model from the issue text.