search

amcharts / amcharts4

The most advanced amCharts charting library for JavaScript and TypeScript apps.
https://www.amcharts.com/
1.15k stars 322 forks source link

[Violation] 'requestAnimationFrame' handler took xx ms #671

Open aniov opened 5 years ago

aniov commented 5 years ago

Lately I saw this warning "[Violation] 'requestAnimationFrame' handler took 570ms" as you can see in the video. I've tried amchart 3 on your demo page and I saw that warning in rare cases.

The problem is that I have about 4-6 graphs on same page and to render them it takes about 3-4 sec. That is not very user friendly. The data in charts have between 20-100 points / graph. Is there a way I can reduce the render time or can you work on this in next releases?

amcharts-warning

martynasma commented 5 years ago

Just letting you know, we are going to investigate this in a non-priority fashion.

It's important to understand, that this is not an actual error. It's an advisory warning. Meaning it does not have any real impact on functionality, but serves as a tip for application developers.

When the chart is building itself, it will try to chunk up the process into smaller increments if it takes too long. This gives browsers some breathing space. Right now this is hardcoded process, but we are implementing configuration options to control it.

Technically, you will be able to reduce the cutoff time, so each chunk is less than Chrome's control 50ms to get rid of the warnings.

BUT (there's always a one) it will come at the expense of risking that chart builds itself gradually. Meaning will see how different elements of the chart appear, as opposed to the chart just popping into place. (to see what I mean try some complex chart in an IE, which is painfully slow)

We're looking for ways to resolve that, too. Not sure how/if/when that will happen. Just wanted you to have the full picture.

sunith-kumar commented 4 years ago

Any updates on addressing this Issue, Because due this other animations in the page are getting affected

CityShark-zz commented 4 years ago

Any news? My console log gets flooded by this...

jannwildelgado commented 4 years ago

Any update for this concern?

YousafRaja commented 4 years ago

I'm also running into this issue.

rebeccadavidsson commented 3 years ago

+1

vvarh commented 3 years ago

I have the same problem on a simple page with a simple graph.

yoricktran commented 3 years ago

I have it too with a pretty standard mapchart

narkissbv commented 3 years ago

I still have this issue. I doubt it will be addressed if this thread is from 2018, and it's 2021 atm.

xbaha commented 3 years ago

me too, please update!

kolgotko commented 3 years ago

+1

nseb commented 3 years ago

Same problem with >4 graphs by page (desktop or mobile). Chartjs no problems and is much faster.

Any updates ?

nseb commented 3 years ago

It's very poor performance

Disame143 commented 3 years ago

I tried downgrading AmCharts 4 version to 4.5.13 and the infinite calling of "[Violation] 'requestAnimationFrame' handler took ms" in console stop but it didn't remove all, there are still warnings seen in console from time to time. Is there any updates for this issue?

ahmedalatawi commented 3 years ago

Any updates on this?

SharpBCD commented 2 years ago

+1

phamvanhan68 commented 2 years ago

Please, do we have any updates on this?

vpattar commented 2 years ago

This really makes UI render very slow. Any update on these warnings?

vincespace commented 2 years ago

Update on this?

Yamilestebangarcia commented 2 years ago

tengo el mismo problema

surray commented 2 years ago

I need an update as well!

heetagna-samyak commented 1 year ago

Did anyone found solution for the same? I am using ngx-pie charts

heetagna-samyak commented 1 year ago

Just letting you know, we are going to investigate this in a non-priority fashion.

It's important to understand, that this is not an actual error. It's an advisory warning. Meaning it does not have any real impact on functionality, but serves as a tip for application developers.

When the chart is building itself, it will try to chunk up the process into smaller increments if it takes too long. This gives browsers some breathing space. Right now this is hardcoded process, but we are implementing configuration options to control it.

Technically, you will be able to reduce the cutoff time, so each chunk is less than Chrome's control 50ms to get rid of the warnings.

BUT (there's always a one) it will come at the expense of risking that chart builds itself gradually. Meaning will see how different elements of the chart appear, as opposed to the chart just popping into place. (to see what I mean try some complex chart in an IE, which is painfully slow)

We're looking for ways to resolve that, too. Not sure how/if/when that will happen. Just wanted you to have the full picture.

The performance is surely affected it is very laggy