Computer Models and Browser Versions FAQ

Symptoms

The DataV editor may stutter with high CPU usage on MacBooks under these conditions:

• MacBook with a Retina display at high resolution.

• Latest Chrome browser version.

• DataV projects with basic flat map widgets.

Cause

A bug in Chrome 66.0.3359.31 on Mac causes excessive CPU usage during canvas rendering, dropping frame rates for pages with canvas widgets (Chromium issue #822417). The effect worsens with more canvas pixels and overlay layers, especially at 1920×1080 resolution with basic flat map widgets.

• During canvas rendering, CPU usage can spike from 3-5% to a sustained 100%, dropping frame rates below 8 fps.

• This affects all web products with canvas-based widgets.

• The issue intensifies with more canvas pixels and overlay layers, particularly at 1920×1080 resolution.

Solutions

This bug was reported to the Chrome team with no fix timeline provided. Use these workarounds:

• Use an earlier Chrome version (57 or later recommended).

• Switch to a different browser, such as Safari.

• Use a Windows computer for editing.

Background

Starting with Chrome 80 (February 4, 2020), Google blocks third-party cookies by default, assigning SameSite=Lax to cookies and rejecting insecure SameSite=None cookies to prevent CSRF vulnerabilities. (Cookies default to SameSite=Lax) (Reject insecure SameSite=None cookies).

Test whether Chrome 80 affects your applications

1. In Chrome, go to chrome://flags/#same-site-by-default-cookies and set SameSite by default cookies to Enabled.

2. Go to chrome://flags/#cookies-without-same-site-must-be-secure and set Cookies without SameSite must be secure to Enabled.

3. Restart Chrome, open your DataV application, and verify that all data returns and displays correctly.

   1. If data returns normally, the upgrade will not affect your application.

   2. If data does not return normally, the upgrade affects your application. Follow the applicable scenario below to resolve the issue.

Scenario 1: API data source

When a component uses an API that requires cookie-based authentication to fetch third-party data:

Impact: The component may not return or display data correctly.

Solution: Check whether the API uses HTTPS or HTTP.

• For HTTPS protocol (Chrome version 95 and above):

Ensure the Set-Cookie response header includes SameSite=None and Secure. If missing, add both attributes to the Set-Cookie header.

• For HTTP protocol (Chrome version 80):

  1. In Chrome, go to chrome://flags/#same-site-by-default-cookies and set SameSite by default cookies to Disabled.

  2. Go to chrome://flags/#cookies-without-same-site-must-be-secure and set Cookies without SameSite must be secure to Disabled.

  3. Restart the browser.

• For HTTP protocol (Chrome versions 91 to 94):

  • In Chrome, go to chrome://flags/, search for same, and set Enable removing SameSite=None cookies to Disabled.

  • Go to chrome://flags/, search for same, and set Schemeful Same-Site to Disabled.

  • Restart Chrome.

Scenario 2: HTTP local deployment

Accessing DataV via HTTP under Chrome 80 may block login, making local deployment services unusable.

Solutions: