Andrzej Kurek

Hi @tadrud, what SFUI version you are using? Try update to latest version first, or pass `persistent=true` prop to login modal. https://docs.storefrontui.io/?path=/story/components-molecules-modal--persistent

Hi @themreza, I believe you could use the proxy server, check out this [PR](https://github.com/vuestorefront/vue-storefront/pull/6334/files#diff-2a4ba52b592e202cf4f9638772a23aac52319f9d2d0aa27ded87b9d0fee655e0)

Try with temporary redirect status ``` [[redirects]] from = "/create-ticket" to = "/.netlify/functions/create-ticket" status=307 //

Does memory, after changes, still hold any _detached_ nodes? I can see memory consumption is fluctuating in provided snapshots. Edge browser offers nice tool for debugging DOM leaks https://docs.microsoft.com/en-us/microsoft-edge/devtools-guide-chromium/memory-problems/dom-leaks

@marc-arnoult I believe the issue apply to nodes that are outside the range of native loading event handler i.e. hidden carousel images, images below the threshold [[link](https://web.dev/browser-level-image-lazy-loading/#distance-from-viewport-thresholds)] that are not...

@AdamPawlinski customized CT E-comm integration, but should be reproductible on the official demo as well https://demo-ct.vuestorefront.io/

If you cannot reproduce with standalone component, my another assumption is this bug might be related with deferred hydration, these project heavily rely on.

@marc-arnoult I can confirm that `SfCarousel` component have a leak, I fixed it locally as well. But its difficult to extract a single reason, why removing `loading=lazy` property from my...