Tìm kiếm hỗ trợ

Tránh các lừa đảo về hỗ trợ. Chúng tôi sẽ không bao giờ yêu cầu bạn gọi hoặc nhắn tin đến số điện thoại hoặc chia sẻ thông tin cá nhân. Vui lòng báo cáo hoạt động đáng ngờ bằng cách sử dụng tùy chọn "Báo cáo lạm dụng".

Learn More

Strava - WebSite - Login - FirefoxCP Web Content using up the RAM

  • Không có trả lời
  • 1 gặp vấn đề này
  • 12 lượt xem
more options

Recently the strava web site login page started using up all the RAM (8GB in total, typically 3-4GB free) on my MAC (OS Mojave) when using Firefox (78.0.2 (64-bit).

FirefoxCP Web Content is the app using up the RAM/Resources.

I suspect this is due to all the trackers strava.com is running and I have firefox setup with 'Enhanced Tracking Protection: Always On'

Blocking Cookies - Cross site and media trackers tracking content - in all windows cryptominers fingerprinters

I always run the Facebook Container.

Note, this problem started about 10-12 days ago, before the garmin ransomware (fwiw).

Note, I don't have any issues with the strava.com/login page consuming resources when using Chrome with Privacy Badger and Adblock Plus.

This is just an FYI - since unsure if it is just a 'my machine' issue. Not ready to test in Firefox without all the enhanced protection yet...

Recently the strava web site login page started using up all the RAM (8GB in total, typically 3-4GB free) on my MAC (OS Mojave) when using Firefox (78.0.2 (64-bit). FirefoxCP Web Content is the app using up the RAM/Resources. I suspect this is due to all the trackers strava.com is running and I have firefox setup with 'Enhanced Tracking Protection: Always On' Blocking Cookies - Cross site and media trackers tracking content - in all windows cryptominers fingerprinters I always run the Facebook Container. Note, this problem started about 10-12 days ago, before the garmin ransomware (fwiw). Note, I don't have any issues with the strava.com/login page consuming resources when using Chrome with Privacy Badger and Adblock Plus. This is just an FYI - since unsure if it is just a 'my machine' issue. Not ready to test in Firefox without all the enhanced protection yet...