MetaMask / MetaMask/metamask-extension
[Sentry] Error: Cannot call write after a stream was destroyed
Open
area-sentry
external-contributor
for-migration
INVALID-ISSUE-TEMPLATE
mig-epic-2-child
regression-prod-11.7.2
Sev2-normal
team-extension-platform
type-bug
- Dominant language
- TypeScript
- Stars
- 13.2k
- Forks
- 5.6k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 451
Description
Sentry Issue: [METAMASK-X88N](https://metamask.sentry.io/issues/5916948622/?referrer=github_integration)
```
Error: Cannot call write after a stream was destroyed
at Error (/metamask/runtime-lavamoat.js:7552:17)
...
(16 additional frame(s) were not displayed)
```
Contributor guide
Research direction
Start with the linked Sentry issue and the stack trace in runtime-lavamoat.js, then investigate which stream operation is occurring after destruction. Reproduce the error if possible and trace it back to the relevant extension path. Done means the cause is identified and the write-after-destroy error no longer occurs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100