Severe memory leak in Linux

[pasunboneleve]

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

[pasunboneleve]

Also if that's relevant:

Firefox 140.0 (64-bit)
Chrome Version 138.0.7204.92 (Official Build) (64-bit)

[pasunboneleve]

Reproduced in NixOS Linux too.

[AlemTuzlak]

Could you try to pinpoint the exact version this started happening? That would GO a long way to help me figure it out

[jmisur]

When I take a bunch of heap snapshots using Chrome's DevTools (ran dev mode using NODE_OPTIONS='--inspect --max-old-space-size=2048' react-router dev), I can see that after while (changing code, navigating) the memory consumption increases. Biggest culprit are json strings of kind "event":"all-route-info". Search on github points to this plugin.

OS: Windows 11
Chrome: 138.0.7204.169
Vite: 6.3.5
devtools: 5.0.6
RR7: 7.7.1

[AlemTuzlak]

@jmisur @dmvianna mind testing out the latest release, I think I figured out and fixed the issue but I don't have a linux system to confirm

[pasunboneleve]

I haven't crashed yet, but I can see that both pages where I have react-router-devtools are now over 5 GB big. It is good I didn't crash. But it looks like you found a workaround, not a solution to memory growing out of control.

[pasunboneleve]

Now 6 GB, the other one went down, probably Firefox being smart at stopping inactive pages. The memory graph is flat though, so at least it doesn't fill the memory completely, but it does take much more memory than one would expect.