Performace issues of clarity with lazyloading or swipe.js

[kwon1206]

If this is an issue you're seeing in https://clarity.microsoft.com please reach out to [email protected] with the details of your bug along with your project ID or a link to your project page.

---

For all other issues continue below:

Please also add all relevant labels from the list of existing ones.

Describe the bug
A clear and concise description of what the bug is.
I applied clarity to our web site(e-commerce) and I suddenly encountered severe performece issue on iPhone.
The phenomenon is reboot or restart the mobile app(or safari browser) with very over use in mobile CPU.
I think it's related with lazyloading and swiping but I'm not sure.

Repro Steps
If applicable, steps to reproduce the behavior.
I removed clarity script due to the performance issus.
But I still use lazy loading and swiping on my site.

Screenshots
If applicable, add screenshots to help explain your problem.
attached screentshot shows the performance metrics about the device which is accessed my site with clarity before.

Project info
If this is an issue happening in a specific project,

• Type: website
• Website info: project ID : i7nl1nyciy, URL : https://m.shilladfs.com/estore/kr/ko/

Browser info:

• OS: iOS
• Browser: Safari

[aschildmeyerSTR]

Not sure if it is related. We pulled Clarity recently from our Blazor Server application. We had found starting December 10th @ ~10:30AM MST that our servers were getting crazy high CPU sustained. Our clients were calling about issues with our app. After doing some diagnosis with performance monitoring tools in browsers, we found on the browser, client side an astronomical increase in javascript calculation time and 100% browser CPU usage. To accelerate the issue, you can use a VM with up to 2 2 vCPU's and 4GB of ram. In this scenario with a lower powered device, it would cause an infinite loop that the app could never pull out of. Meanwhile it would drive up the client CPU 100%. We observed for every idle callback for clarity it was taking 1.8ms on a good computer. Where an underpowered device or a device already heavily taxed it was more like 18ms per idle callback. The queue for js could never clear the workload on those systems. We are never going to use clarity again as it hurt on reputation.

Prior, we were using Clarity for over a year without issues.