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

Slow/Unresponsive UI starting Jambi 6.4.2 #125

Closed
ygorodnitsky opened this issue Jan 11, 2023 · 2 comments
Closed

Slow/Unresponsive UI starting Jambi 6.4.2 #125

ygorodnitsky opened this issue Jan 11, 2023 · 2 comments

Comments

@ygorodnitsky
Copy link

Using QT 6.4.1 We experienced signficant UI performance degradation starting with Jambi 6.4.2. As if the UI thread is being paced/overwhelmed.
I created a prototype project. This is an intentionally large table with moderately quick updates. It loads in 6.4.1 -- The window may have some responsiveness issue when resizing, but otherwise scrolling is smooth and easy. In our application we have a different window qml class, so resizing isn't handled by the OS, so it's not an issue, for this example scrolling and general UI responsiveness is the main problem.
BigTableProblem.zip

With 6.4.2 the app hangs and doesn't load to even try to do anything.

@mchistovib
Copy link

@omix please have a look

@omix
Copy link
Contributor

omix commented Jan 12, 2023

I've foud the reason for this behaviour. Latest QtJambi release has native QModelIndex type. Before it was lightweight. The native implementation of QModelIndex needs a dependency link to the model because Java object has to be invalid when model is deleted. This link is causing high computational effort because of a hash map contains check. This is only recognizable for huge numbers of objects, which you have. I will fix this for the next release.

omix added a commit that referenced this issue Jan 19, 2023
Bugfix Issue #125
Bugfix Issue #118
@omix omix closed this as completed Jan 24, 2023
omix added a commit that referenced this issue Jul 25, 2023
Bugfix Issue #125
Bugfix Issue #118
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

3 participants