On nonexistent image request, next/image hangs and eventually returns a 504

[inside]

Run next info (available from version 12.0.8 and up)

    Operating System:
      Platform: linux
      Arch: x64
      Version: #51~20.04.1-Ubuntu SMP Fri Jan 7 06:51:40 UTC 2022
    Binaries:
      Node: 16.13.0
      npm: 6.14.15
      Yarn: 1.22.15
      pnpm: 6.11.0
    Relevant packages:
      next: 12.0.9-canary.0
      react: 17.0.2
      react-dom: 17.0.2

What version of Next.js are you using?

12.0.9-canary.0

What version of Node.js are you using?

16.13.0

What browser are you using?

Chrome

What operating system are you using?

Linux

How are you deploying your application?

Local application

Describe the Bug

On nonexistent image request, next/image hangs and eventually returns a 504.

This happens in a local next app and also in our production app.

Expected Behavior

next/image should return a 404

To Reproduce

Please have a look at this repo where you can find the steps to reproduce: https://github.com/inside/next-image-app

[thibautsabot]

Hi!

After some investigations it seems to hang on this instruction https://github.com/vercel/next.js/blob/canary/packages/next/server/image-optimizer.ts#L291.

Note that is is working as intended (returning a 404) on node < 16.
15.14.0 (latest v15) -> 404
16.0.0 (first v16) -> hangs

[kyliau]

The following test should have caught this bug but I'm not sure why it doesn't happen in CI.
On my local machine the test hangs.

next.js/test/integration/image-optimizer/test/index.test.js

Lines 774 to 780 in eaf680d

	it("should error if the resource isn't a valid image", async () => {
	const query = { url: '/test.txt', w, q: 80 }
	const opts = { headers: { accept: 'image/webp' } }
	const res = await fetchViaHTTP(appPort, '/_next/image', query, opts)
	expect(res.status).toBe(400)
	expect(await res.text()).toBe("The requested resource isn't a valid image.")
	})

[github-actions]

This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.