code-forge-io / code-forge-io/react-router-devtools
Severe memory leak in Linux
- Vorherrschende Sprache
- TypeScript
- Sterne
- 972
- Forks
- 55
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Beschreibung
We recently adopted `react-router-devtools` in my team.
`vite.config.ts`
```typescript
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
Beitragsleitfaden
Für dieses Repository ist kein Beitragsleitfaden indexiert
Rechercherichtung
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.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- linux, react, typescript, vite
- Bereich
- devtools, operating-systems, performance, tooling
- Issue-Typ
- Bug
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Aktivitätsstatus
- Veraltet
- Klarheit
- Muss geklärt werden
- Anfängerfreundlichkeit
- 25/100