Back browser button strange behavior

[StadnykYura]

In our project we use NextJs App for initial rendering of the application on server, then the page is cached on cdn and all other subsequent user navigation is done with React-router/react-router-dom behaving like SPA. So we don`t go to the server on browser navigation, and NextJs Links are not used.
We also use [[..slug]] (all routes dynamic) for handling every request. This is current architecture due too complications of the project and recent migration to SSR and NextJs.

The problem we recently faced is:

1. you open SSR rendered page (multiple product page with some grid specifically),
2. you apply several filters (3 times) which changes the url and pathname on each filter applied
3. you reload the page with browser button
4. click the browser back button, and app becomes laggy or even can become unresponsive at all (doesn`t respond to any actions, only url changes on links clicking, but nothing is happening on the page) on subsequent back button clicks:

• it is doing long computations (the stacktrace goes to dispatch function which we do in client component called StoreInitializer where we initialize our redux store based on received RSC payload as props from server component);
  

• the last long task also has huuuuge stack trace of same recursive functions ( the trace is much much longer) on the next screen:
  

• This top lvl Client component StoreInitializer, that previoulsy received some props from Server Components as RSC payload, throws some warnings on that back button click
  

There is no problem when the page is not reloaded on step '3'.
My question is::

1. How NextJs handles the back browser button after the page reload?,
2. Could it be some conflict with RSC payload when the back browser button was clicked after the reload, so the application doesn`t know what was the actual payload there?
3. How can we possibly/correctly handle it within our architecture