Permanently high CPU utilization after sorting

I’m submitting a … (check one with “x”)

[X] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here

Current behavior

Permanently high cpu utilization after sorting. The utilization will stay high till the tab is reloaded. Also after another sort the cpu utilization will increase permanently (up to 100%). Expected behavior After sorting the cpu utilization should go down to <10%.

Reproduction of the problem Reproducible in your demo, just click sort in the demo, wait a bit or click a bit around. The cpu utilization will remain on a high level.

What is the motivation / use case for changing the behavior? Lags after sorting

Please tell us about your environment:

Arch Linux 4.8.11 Chromium Version 55.0.2883.75 (64-bit) Firefox Version 50.0.2 CPU: i5 2500k@ 4,4Ghz, 24GB of RAM HW Acceleration enabled (Only Native GpuMemoryBuffers and Rasterization HW acceleratiion disabled)

• Table version: 2.2.0 Version in the current demo (2.2.0)

• Angular version: 2.3.0 Version in the current demo for version 2.2.0

[JanCejka]

Issue is probably in the code that adds & removes “sort-desc” / “icon-up” classes on span.sort-btn element. If you inspect this element, it looks like list of classes is “flickering”. If you break on attributes modification of this span element, you would get pretty instant breaks where you see that these two classes are being removed and re-added very fast. I have seen this behavior in version 2.2.1 and it’s present in live demo on http://swimlane.github.io/angular2-data-table/ as well (e.g. Client-side sorting and then clicking on column to sort).

[Thoma5]

Thanks, works fine now!