Severe memory leak in Linux
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- linux, react, typescript, vite
- Domain
- devtools, operating-systems, performance, tooling
Research direction
Start with the vite.config.ts configuration and reproduce the memory growth on Fedora Linux 42 using react-router-devtools 5.0.6, comparing development runs with the devtools enabled and disabled. Use the reported Chrome or Firefox behavior to identify the leak; done means browsing no longer causes continued memory growth or a crash on Linux.
Written by the indexing model from the issue text.
Description
We recently adopted react-router-devtools in my team.
vite.config.ts
export default defineConfig({
plugins: [
process.env.NODE_ENV === "development" ? reactRouterDevTools() : undefined,
tsconfigPaths({ root: "./", projects: ["tsconfig.json"] }),
tailwindcss(),
reactRouter()
],
optimizeDeps: {
exclude: ["google-auth-library", "gcp-metadata"],
},
})
In development mode, only in Linux, browsing through my application leads to a rapid increase in memory use
in both Chrome and Firefox. Running the application without react-router-devtools leads to no issue, and using react-router-devtools in MacOS also leads to no issue.
After minutes of not interacting with the page at all, it crashes.
System
Fedora Linux 42 (Workstation Edition)
Packages
- react-router-devtools 5.0.6
- Dominant language
- TypeScript
- Stars
- 975
- Forks
- 55
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing 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.
More from code-forge-io/react-router-devtools
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 3/5 1-2 days Newbie friendliness 30/100
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
-
Difficulty 3/5 1-2 days Newbie friendliness 38/100
code-forge-io/react-router-devtools#247 · 12 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
code-forge-io/react-router-devtools#243 · 1 comment ·
All issues in code-forge-io/react-router-devtools
Similar issues
-
bug(core): JsonOutputKeyToolsParser ignores returnId: truePossibly taken A pull request linked to this issue is open or already merged. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
langchain-ai/langchainjs#12239 ·
Maintainers usually reply within 1 day
-
Board view: the Monitoring column is always empty because compact issue rows drop displayStatusOpen
Difficulty 1/5 Under an hour Newbie friendliness 88/100
paperclipai/paperclip#21837 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
code-yeongyu/senpi#6813 ·
Maintainers usually reply within 1 day
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 93/100
lingdojo/kana-dojo#34169 · 1 comment · 5 reactions ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100