Crash report: `NotFoundError: Node.removeChild: The node to be removed is not a child of this node`
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.5k
- Forks
- 5.4k
- PR merge metrics
- No merged PRs in 30d
Description
URL
https://app.uniswap.org/#/swap?chain=mainnet
swap state
{
"INPUT": {
"currencyId": "0x7ceB23fD6bC0adD59E62ac25578270cFf1b9f619"
},
"OUTPUT": {
"currencyId": "0x2791Bca1f2de4661ED88A30C99A7a9449Aa84174"
},
"independentField": "INPUT",
"typedValue": "6.747563835233757206",
"recipient": null
}
Error
NotFoundError: Node.removeChild: The node to be removed is not a child of this node
Stacktrace
Ea@https://app.uniswap.org/static/js/2.4d4a6dc4.chunk.js:2:2603161
Fs@https://app.uniswap.org/static/js/2.4d4a6dc4.chunk.js:2:2614953
t.unstable_runWithPriority@https://app.uniswap.org/static/js/2.4d4a6dc4.chunk.js:2:2635501
Jf@https://app.uniswap.org/static/js/2.4d4a6dc4.chunk.js:2:2558041
Rs@https://app.uniswap.org/static/js/2.4d4a6dc4.chunk.js:2:2612911
ws@https://app.uniswap.org/static/js/2.4d4a6dc4.chunk.js:2:2608995
Qf/<@https://app.uniswap.org/static/js/2.4d4a6dc4.chunk.js:2:2558264
t.unstable_runWithPriority@https://app.uniswap.org/static/js/2.4d4a6dc4.chunk.js:2:2635501
Jf@https://app.uniswap.org/static/js/2.4d4a6dc4.chunk.js:2:2558041
Qf@https://app.uniswap.org/static/js/2.4d4a6dc4.chunk.js:2:2558211
Yf@https://app.uniswap.org/static/js/2.4d4a6dc4.chunk.js:2:2558144
Fe@https://app.uniswap.org/static/js/2.4d4a6dc4.chunk.js:2:2629311
Qt@https://app.uniswap.org/static/js/2.4d4a6dc4.chunk.js:2:2536776
Device data
{
"ua": "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Firefox/102.0",
"browser": {
"name": "Firefox",
"version": "102.0",
"major": "102"
},
"engine": {
"name": "Gecko",
"version": "102.0"
},
"os": {
"name": "Windows",
"version": "10"
},
"device": {},
"cpu": {
"architecture": "amd64"
}
}
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 crash at the reported swap URL with the supplied state in Firefox 102, then trace the minified stack back to the application source. Done means the same swap flow no longer raises the Node.removeChild error, with an appropriate regression check if the project has coverage for this path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100