Bugzilla

(In reply to florian.greinus from Bug 1645325 comment #8)
> Here my feedback - sorry that it took so long!
> 
> https://github.com/fgreinus/react-spa-firefox-leak. You can just clone it, run npm install (or use yarn, just as you like) and then use yarn start or npm run start. Your browser should open for localhost:3000. Then just go into App.js and change something, save and the browser will automatically reload the SPA according to your changes. This is already the moment where it start's leaking (from what i have seen). Memory report diffs also show that. More often reloads (saves) lead to more memory and bigger size leads to more significant leaks (quite obvious though).
> 
> Hope this helps!

Hot reload sample app provided by :florian.greinus on another similar bug

(In reply to florian.greinus from Bug 1645325 comment #8)
>
> https://github.com/fgreinus/react-spa-firefox-leak. You can just clone it, run npm install (or use yarn, just as you like) and then use yarn start or npm run start. Your browser should open for localhost:3000. Then just go into App.js and change something, save and the browser will automatically reload the SPA according to your changes. This is already the moment where it start's leaking (from what i have seen). Memory report diffs also show that. More often reloads (saves) lead to more memory and bigger size leads to more significant leaks (quite obvious though).
> 
> Hope this helps!