React editor slows down to become unusable when hot-reloading many images

🐛 bug report

Preflight Checklist

• I have read the Contributing Guidelines for this project.
• I agree to follow the Code of Conduct that this project
  adheres to.
• I have searched the issue tracker for an issue that matches the one I want
  to file, without success.

Description of the problem

React editor slows down to become unusable when hot-reloading many images

How has this issue affected you? What are you trying to accomplish?

I was using CodeSandbox during an interview for React/TypeScript, where the problem involved displaying many images. When I started generalizing the <img> into its own component, suddenly the editor would say things like "<some variable name I hadn't finished typing> is not defined" (but only when I was working with the "src" parameter) over and over in what looked like an infinite loop of "Problems" with the counter ticking up to the thousands of the same message, slowing down the tab until Chrome let me kill it as "not responding."

Refreshing did not work. I worked around this by copying all the code before the tab slowed down too much, closing it and reopening it. Sometimes, even after closing and reopening, I still had to wait for Chrome to bail out of loading the blank page so I could kill it, which I found odd, and maybe a Chrome-specific thing. I kept trying to turn off hot-reloading, but I couldn't find out how to do this.

To Reproduce

Create a sandbox that tries to fetch ~200 images from different URLs, and trigger re-renders of all the images, by, say, changing the variable name used in the src parameter of the <img> tag. I think the high volume of images fetched contributed to the bug because I wasn't able to reproduce this on a minimal working example.

It also doesn't seem to have any relation to an actual React error - I did, say, cause a standard React "too many re-renders" error with no issues at all, which is what I thought this was at first.

Link to sandbox: link (optional)

This is the exact sandbox I used during the interview, but I've redacted anything that ties this code to the actual interview/company.

Here's a screenshot of what it looks like while the tab slows down. Notice I'm trying to finish typing "src", but the flood of "s is not defined" making the page slow to a crawl isn't letting me do so.

Your Environment

Start with the linked CodeSandbox at src/App.js and reproduce the slowdown using about 200 image URLs and repeated edits to the img src value. Compare the Problems flood and hot-reload behavior before and after the change; done means the editor remains usable without accumulating thousands of repeated diagnostics.