-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
High cpu usage when drawing a table with 288 items #4156
Comments
Thanks for the report. There have been quite a lot of changes to the Table widget for the upcoming release. Would you mind trying out the |
A little better cpu usage. muchr snappier. also it does not extensively call the update function 👍🏻 Resizing the window so it's smaller than the table and then dragging it out bigger again crashes the test code tougt :/ |
Can you provide the crash log so we can test against it please? Sounds like something that needs fixed for release. |
it doesn't crash today when i try it so wondering if it is some racecondition that made the window lock up yesterday |
Did it crash or hang before? P.s. I think you're missing calls to Show() and Enable() in your test code |
I cannot see any CPU usage when the table is displayed. Perhaps this is a duplicate of #1946? |
Checklist
Describe the bug
Displaying a simple table uses 6-14% CPU on a Intel i9-9900k.
Moving the mouse pointer around in the window spikes 1 core to almost 100% CPU
clicking and marking a cell is noticeably laggy and takes upwards half a second for the blue border to move
I can see the update function is constantly being called just by moving the mouse pointer in the window which might be the culprit causing it to call SetText on all 288 entries even though nothing changed
How to reproduce
Run example program which has 288 data points that needs to be displayed in the table
Screenshots
No response
Example code
Fyne version
2.3.5
Go compiler version
1.21
Operating system and version
Windows 11
Additional Information
No response
The text was updated successfully, but these errors were encountered: