Receiving message d[1].diff is not a function


I have been using Metabase for a while, but I am experiencing some weird behavior right now.

I can generate all information properly (Table:

It turns out, when I try to generate some chart (any type), I receive this message d[1].diff is not a function with the exclamation icon above.

I tried to identify what is happening, comparing with other charts I have, but there are others with the same information format, and they are working.

I need some help to understand this issue, since I am running out of ideas.

Thank you

Hi @viniciusnordi
Please post “Diagnostic Info” from Admin > Troubleshooting.
Do you have a reverse-proxy or CDN (like CloudFlare) in front of Metabase? Disable any minimization/optimization they might have enabled.
It could also be an aggressive antivirus or extension in your browser that is causing it.

Hello @flamber, thank you for the response.

The Diagnostic Info follows:

  "browser-info": {
    "language": "pt-BR",
    "platform": "Linux x86_64",
    "userAgent": "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/77.0.3865.75 Safari/537.36",
    "vendor": "Google Inc."
  "system-info": {
    "": "OpenJDK Runtime Environment",
    "java.runtime.version": "11.0.5+10",
    "java.vendor": "AdoptOpenJDK",
    "java.vendor.url": "",
    "java.version": "11.0.5",
    "": "OpenJDK 64-Bit Server VM",
    "java.vm.version": "11.0.5+10",
    "": "Linux",
    "os.version": "4.15.0-50-generic",
    "user.language": "en",
    "user.timezone": "GMT"
  "metabase-info": {
    "databases": [
    "hosting-env": "unknown",
    "application-database": "postgres",
    "run-mode": "prod",
    "version": {
      "date": "2019-12-23",
      "tag": "v0.34.0-snapshot",
      "branch": "master",
      "hash": "3775a3a"
    "settings": {
      "report-timezone": "UTC"

I don’t have any CDN in front of metabase. And there is only one chart that is not working. Any other works perfectly.

@viniciusnordi Okay, you’re not using one of the official releases, so that’s most likely the problem. And even if you upgrade to a release, then the problem might have been created by the snapshot you used, so re-create the question and delete/archive the problematic question.