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

StandardTableView causes the CPU to occupy 100%, and then the UI freezes #5041

Open
vonnieda opened this issue Apr 10, 2024 Discussed in #3601 · 2 comments
Open

StandardTableView causes the CPU to occupy 100%, and then the UI freezes #5041

vonnieda opened this issue Apr 10, 2024 Discussed in #3601 · 2 comments

Comments

@vonnieda
Copy link

Discussed in #3601

Please see comment for full details and a short test case.

In short, when scrolling the StandardTableView quickly, there are huge spikes in CPU and the frame rate drops to 0. This is happening even in a simple table with 100 rows of 6 text columns, which is demonstrated in the attached app. If you bump it up to 1000 rows you start getting complete UI lockups with Mac beach balls, and 10k rows is unusable.

@vonnieda
Copy link
Author

Video to show the issue attached:

Screen.Recording.2024-04-11.at.4.44.43.PM.mov

@vonnieda
Copy link
Author

I've confirmed (after simon asked on Mattermost) that this is a regression that happened between 1.4.1 and 1.5.0, and also exists on 1.5.1.

This can be seen in the test case posted at https://github.com/slint-ui/slint/files/14938821/my-project.zip by changing the slint dependency to "= 1.4.1" or "= 1.5.0", and changing the row count to 1000.

In 1.4.1 using the mouse wheel to scroll the list (or dragging the thumb) is smooth. In 1.5.0+ there are big jumps in lag, beachball timeouts, FPS = 0, etc.

Discussed with simon here: https://chat.slint.dev/public/pl/a8jn76pua3nr8xdbq8q49dasww

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

No branches or pull requests

1 participant