[Violation]'requestAnimationFrame' handler took

[yuwencheng0212]

I'm submitting a ... (check one with "x")

Cesium.js:12477 [Violation]'requestAnimationFrame' handler took 589ms
Cesium.js:12477 [Violation]'requestAnimationFrame' handler took 681ms
Cesium.js:12477 [Violation]'requestAnimationFrame' handler took 587ms
Cesium.js:12477 [Violation]'requestAnimationFrame' handler took 643ms
Cesium.js:12477 [Violation]'requestAnimationFrame' handler took 602ms
Cesium.js:12477 [Violation]'requestAnimationFrame' handler took 664ms
Cesium.js:12477 [Violation]'requestAnimationFrame' handler took 560ms
Cesium.js:12477 [Violation]'requestAnimationFrame' handler took 613ms
Cesium.js:12477 [Violation]'requestAnimationFrame' handler took 592ms
Cesium.js:12477 [Violation]'requestAnimationFrame' handler took 683ms
Cesium.js:12477 [Violation]'requestAnimationFrame' handler took 540ms
Cesium.js:12477 [Violation]'requestAnimationFrame' handler took 607ms
Cesium.js:12477 [Violation]'requestAnimationFrame' handler took 568ms
Cesium.js:12477 [Violation]'requestAnimationFrame' handler took 643ms
Cesium.js:12477 [Violation]'requestAnimationFrame' handler took 655ms
Cesium.js:12477 [Violation]'requestAnimationFrame' handler took 856ms
Cesium.js:12477 [Violation]'requestAnimationFrame' handler took 808ms

Current behavior

Expected behavior

Reproduction of the problem
Constantly calling requestAnimationFrame causes the page to freeze. But I couldn't find requestID to stop it.

What is the motivation / use case for changing the behavior?

Please tell us about your environment:

• Table version:

• Angular version:

• Browser: [Microsoft Edge 110.0.1587.63 ]

• Language: [Vue| JavaScript ]