MetaMask / MetaMask/metamask-extension
[Bug]: Platform - `ExtensionPortStream postMessage failed` `Could not serialize message.`
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13.2k
- Forks
- 5.6k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 451
Description
Describe the bug
Minting a huge number of NFTs throws errors ExtensionPortStream postMessage failed Could not serialize message. , then I cannot Confirm or Reject that tx (maybe wallet is frozen bc of performance? or bc of that error? unsure)
Expected behavior
No response
Screenshots/Recordings
https://github.com/user-attachments/assets/67271677-7ab2-49e8-beec-16fa96688fc6
Steps to reproduce
- Go to the test dapp
- Deploy an ERC7212 contract
- Mint 500 tokens
- Confirm
- Mint again 500 tokens
- See error port stream
- Click Confirm Cancel --> nothing happens
Error messages or log output
Where was this bug found?
Internal release testing
Version
13.22.0 (but may be in prod too--checking)
Build type
None
Browser
Chrome
Operating system
MacOS
Hardware wallet
No response
Additional context
No response
Severity
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the test dapp and reproduce the issue by deploying an ERC7212 contract, minting 500 tokens twice, and confirming the transaction in Chrome on macOS. Trace the ExtensionPortStream serialization failure and determine why Confirm or Cancel stops responding. Done means the reported error no longer blocks the transaction flow under this reproduction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100