Repository: next.js
Issue: Error `TypeError: e._formData.get is not a function` while running serverAction in client component, only on dev env 
Labels: bug,Pages Router

### Link to the code that reproduces this issue

https://github.com/Justinyu1618/nextjs-issue-test

### To Reproduce

The issue happens inconsistently, and only when running the dev server. Try running a server action inside a client component. You may need to make a few edits or have the dev server continuously running for a while. 

1. Clone the attached repo, which runs a server action inside a client component
2. `yarn dev`
3. Try refreshing the page several times, or make some edits. At some point, the issue may occur. After the issue occurs, any calls to serverActions are broken

### Current vs. Expected behavior

Expected behavior: the server action is run 

Current behavior: The dev server sometimes gets into a state where it will throw this error (below) whenever a server action is called from inside a client component. Sometimes, rerunning the dev server fixes it but not always. It doesn't matter what the server action is doing, it will continue throwing this error. 
If you `yarn build && yarn start`, the issue no longer exists 

```
TypeError: e._formData.get is not a function
    at tn (/Users/justinyu/Documents/work/counsel/counsel-main/node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js:35:303107)
    at t.decodeReply (/Users/justinyu/Documents/work/counsel/counsel-main/node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js:35:306681)
    at /Users/justinyu/Documents/work/counsel/counsel-main/node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js:39:284
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async t0 (/Users/justinyu/Documents/work/counsel/counsel-main/node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js:38:5773)
    at async rh (/Users/justinyu/Documents/work/counsel/counsel-main/node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js:39:23636)
    at async doRender (/Users/justinyu/Documents/work/counsel/counsel-main/node_modules/next/dist/server/base-server.js:1391:30)
    at async cacheEntry.responseCache.get.routeKind (/Users/justinyu/Documents/work/counsel/counsel-main/node_modules/next/dist/server/base-server.js:1552:28)
    at async DevServer.renderToResponseWithComponentsImpl (/Users/justinyu/Documents/work/counsel/counsel-main/node_modules/next/dist/server/base-server.js:1460:28)
    at async DevServer.renderPageComponent (/Users/justinyu/Documents/work/counsel/counsel-main/node_modules/next/dist/server/base-server.js:1843:24)
    at async DevServer.renderToResponseImpl (/Users/justinyu/Documents/work/counsel/counsel-main/node_modules/next/dist/server/base-server.js:1881:32)
    at async DevServer.pipeImpl (/Users/justinyu/Documents/work/counsel/counsel-main/node_modules/next/dist/server/base-server.js:909:25)
    at async NextNodeServer.handleCatchallRenderRequest (/Users/justinyu/Documents/work/counsel/counsel-main/node_modules/next/dist/server/next-server.js:266:17)
    at async DevServer.handleRequestImpl (/Users/justinyu/Documents/work/counsel/counsel-main/node_modules/next/dist/server/base-server.js:805:17)
```

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 22.4.0: Mon Mar  6 20:59:58 PST 2023; root:xnu-8796.101.5~3/RELEASE_ARM64_T6020
Binaries:
  Node: 20.10.0
  npm: 10.2.3
  Yarn: 1.22.21
  pnpm: N/A
Relevant Packages:
  next: 14.0.5-canary.58
  eslint-config-next: 14.0.4
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.3.3
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Not sure, App Router, Data fetching (gS(S)P, getInitialProps)

### Which stage(s) are affected? (Select all that apply)

next dev (local)

### Additional context

The error is not consistent. It only comes after working for a bit on the dev server. It does not go away if I try removing the `.next` folder. It also does not go away if I try to clear cache