MetaMask / MetaMask/metamask-extension
ObjectMultiplex liveness warnings and MaxListenersExceededWarning in contentScript.js
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13.2k
- Forks
- 5.6k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 451
Description
What is this about?
Browser:
Brave 1.92.89 (Official Build) nightly (64-bit)
Chromium: 148.0.7778.179
OS: Linux
MetaMask version: 13.32.1
Console warnings:
- MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 close listeners added
- MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 end listeners added
- ObjectMultiplex - orphaned data for stream "app-init-liveness"
- ObjectMultiplex - orphaned data for stream "background-liveness"
- ObjectMultiplex - malformed chunk without name "[object Object]"
Scenario
No response
Design
No response
Technical Details
No response
Threat Modeling Framework
No response
Acceptance Criteria
No response
Stakeholder review needed before the work gets merged
- Engineering (needed in most cases)
- Design
- Product
- QA (automation tests are required to pass before merging PRs but not all changes are covered by automation tests - please review if QA is needed beyond automation tests)
- Security
- Legal
- Marketing
- Management (please specify)
- Other (please specify)
References
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 by reproducing the listed warnings in contentScript.js using the reported Brave, Chromium, Linux, and MetaMask versions. Trace ObjectMultiplex handling for the app-init-liveness and background-liveness streams, along with the close and end listeners; done means the reported liveness, malformed-chunk, and MaxListenersExceededWarning messages no longer occur.
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
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100