slowlydev
slowlydev
> first thing i noticed: we need to proxy the request as we are getting blocked by cors Okay thanks for checking 👍🏻 > second thing: can someone help me...
Yes I also have noticed that. Is either or a combination between framer-motion, the react keys on the map children, or the map in general.
Yes I also noticed that, its probably a combination of caching between nextjs and the api-backend.
I think this got fixed by #247 W'll reopen when it occurs again.
Thanks for the issue, okay I will investigate this Firefox when I have time. If u want to you could run this in the browser console of the f1-dash tab...
Oh wow yeah, each buffer has a 1000 limit so we would be no where near the limits. Has this issue always been there or was it introduced lately?
Hm I did not seem to get the excessive leak you did. But I was also using firefox nightly and I am on arm macOS. I will test on a...
Thanks for the testing. Looks like the buffer changes did not fix the memory leaks. > It seemed to be proportional to the delay, if I had 0 delay there...
The Firefox memory issues have been on https://dev.f1-dash.com and the fix will arrive in prod soon.
> Any update on this? still needs some adjustments and also the lates changes need to be merged into it as well. I hope I can pick this up some...