Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Charts not working in Chromium 78 with chart.js 3.6.1 or 3.6.2 #9980

Closed
ziggi opened this issue Dec 12, 2021 · 5 comments
Closed

Charts not working in Chromium 78 with chart.js 3.6.1 or 3.6.2 #9980

ziggi opened this issue Dec 12, 2021 · 5 comments

Comments

@ziggi
Copy link

ziggi commented Dec 12, 2021

Expected Behavior

I want to see the chart.

Current Behavior

app.17794af6.js:6 TypeError: 'getPrototypeOf' on proxy: trap returned neither object nor null
    at Function.getPrototypeOf (<anonymous>)
    at En (app.17794af6.js:1)
    at app.17794af6.js:1
    at app.17794af6.js:1
    at jn (app.17794af6.js:1)
    at Object.get (app.17794af6.js:1)
    at sn.update (app.17794af6.js:12)
    at new sn (app.17794af6.js:12)
    at o.update (3.e2fd7cce.js:14)
    at We (app.17794af6.js:6)

Steps to Reproduce

Context

I know that version 78 is very old, but it is used as embedded in some software.

Environment

  • Chart.js version: 3.6.1, 3.6.2
  • Browser name and version: Chromium 78
@kurkle
Copy link
Member

kurkle commented Dec 12, 2021

Probably caused by #9861

@kurkle
Copy link
Member

kurkle commented Dec 15, 2021

This is a bug in that old V8: https://bugs.chromium.org/p/v8/issues/detail?id=9781

Can reproduce by running this on console:

Object.getPrototypeOf(new Proxy(Object.create(null), {
  getPrototypeOf(target) {
    return Reflect.getPrototypeOf(target)
  }
}))

There is no easy way of fixing this without other regressions, so its a wontfix.

@uuau99999
Copy link

Can reproduce same issue in 3.7.1 with chrome 77

@LeeLenaleee
Copy link
Collaborator

As described here all modern and up-to-date browsers are supported. Chrome version 77 came out 2,5 years ago. So it is not really up to date. And as @kurkle pointed out it is a bug in the V8 engine of chrome itself without an easy way for us to fix it so we wont do anything about it.

Only thing you can do to resolve it is upgrade chrome to a up to date version where at least the bug in V8 is fixed or downgrade chart.js to version 3.6.0 since its likely the bugg started in 3.6.1

@pnvskp
Copy link

pnvskp commented Jan 5, 2023

I am facing this error even in Chromium version 108.0.5359.128 and Chart.js version 3.9.1

image

Is there any way to fix this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants