-
Notifications
You must be signed in to change notification settings - Fork 188
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
UI freeze when searching over large files. Search View Filter viewer limit is not applied for children in TreeViewer. #2279
Comments
Currently viewer limit is applied to top level elements. Object[] getChildren(Object parentElement) missing limit application. see eclipse-platform#2279
Can you please provide screenshot how you search and what the result looks like? Is this a linux issue only? |
Currently viewer limit is applied to top level elements. Object[] getChildren(Object parentElement) missing limit application. see eclipse-platform#2279
Currently viewer limit is applied to top level elements. Object[] getChildren(Object parentElement) missing limit application. see eclipse-platform#2279
If the search view shows ~100000 matches, deleting resources that are shown in the search view freezes Eclipse for many minutes. With this change the freeze is only about 30 seconds. See eclipse-platform#2279
Currently viewer limit is applied to top level elements. Object[] getChildren(Object parentElement) missing limit application. see #2279
If the search view shows ~100000 matches, deleting resources that are shown in the search view freezes Eclipse for many minutes. With this change the freeze is only about 30 seconds. See eclipse-platform#2279
If the search view shows ~100000 matches, deleting resources that are shown in the search view freezes Eclipse for many minutes. With this change the freeze is only about 30 seconds. See #2279
After playing a bit more with search view after merged changes I saw two things:
I will push a PR addressing both issues in a moment. |
This change unifies "filter" label handling for tree/table mode in the file search, we show now that the matches are filtered in both cases. See eclipse-platform#2279
If the search view has matches for 100.000 files, it would hang forever on updating the view via F5 because it asks getMatchCount() for every element and that traverses entire result again and again. This change remembers last computed result and returns that value if there were no further changes on the search result itself. See eclipse-platform#2279
See #2320 |
Once we have fixe this. Is this something we should also put into the New & Noteworthy document? |
we had performance improvements in every version. But at the same time we have so many regressions that it feels odd to praise xyz got faster while people complain uvw became worse. |
This change unifies "filter" label handling for tree/table mode in the file search, we show now that the matches are filtered in both cases. See eclipse-platform#2279
If the search view has matches for 100.000 files, it would hang forever on updating the view via F5 because it asks getMatchCount() for every element and that traverses entire result again and again. This change remembers last computed result and returns that value if there were no further changes on the search result itself. See eclipse-platform#2279
This change unifies "filter" label handling for tree/table mode in the file search, we show now that the matches are filtered in both cases. See #2279
If the search view has matches for 100.000 files, it would hang forever on updating the view via F5 because it asks getMatchCount() for every element and that traverses entire result again and again. This change remembers last computed result and returns that value if there were no further changes on the search result itself. See #2279
All planned fixes merged, closing. |
Currently viewer limit is applied to top level elements. Object[] getChildren(Object parentElement) missing limit application. see eclipse-platform#2279
If the search view shows ~100000 matches, deleting resources that are shown in the search view freezes Eclipse for many minutes. With this change the freeze is only about 30 seconds. See eclipse-platform#2279
This change unifies "filter" label handling for tree/table mode in the file search, we show now that the matches are filtered in both cases. See eclipse-platform#2279
If the search view has matches for 100.000 files, it would hang forever on updating the view via F5 because it asks getMatchCount() for every element and that traverses entire result again and again. This change remembers last computed result and returns that value if there were no further changes on the search result itself. See eclipse-platform#2279
Currently viewer limit is applied to top level elements. Object[] getChildren(Object parentElement) missing limit application. see eclipse-platform#2279
If the search view shows ~100000 matches, deleting resources that are shown in the search view freezes Eclipse for many minutes. With this change the freeze is only about 30 seconds. See eclipse-platform#2279
This change unifies "filter" label handling for tree/table mode in the file search, we show now that the matches are filtered in both cases. See eclipse-platform#2279
If the search view has matches for 100.000 files, it would hang forever on updating the view via F5 because it asks getMatchCount() for every element and that traverses entire result again and again. This change remembers last computed result and returns that value if there were no further changes on the search result itself. See eclipse-platform#2279
If the search view shows ~100000 matches, deleting resources that are shown in the search view freezes Eclipse for many minutes. With this change the freeze is only about 30 seconds. See eclipse-platform#2279
This change unifies "filter" label handling for tree/table mode in the file search, we show now that the matches are filtered in both cases. See eclipse-platform#2279
…hanges#2288 Bump bundle version after API change See eclipse-platform#2279
If the search view shows ~100000 matches, deleting resources that are shown in the search view freezes Eclipse for many minutes. With this change the freeze is only about 30 seconds. See eclipse-platform#2279
…he tree mode This change unifies "filter" label handling for tree/table mode in the file search, we show now that the matches are filtered in both cases. See eclipse-platform#2279
If the search view has matches for 100.000 files, it would hang forever on updating the view via F5 because it asks getMatchCount() for every element and that traverses entire result again and again. This change remembers last computed result and returns that value if there were no further changes on the search result itself. See eclipse-platform#2279
If the search view shows ~100000 matches, deleting resources that are shown in the search view freezes Eclipse for many minutes. With this change the freeze is only about 30 seconds. See eclipse-platform#2279
If the search view shows ~100000 matches, deleting resources that are shown in the search view freezes Eclipse for many minutes. With this change the freeze is only about 30 seconds. See eclipse-platform#2279
If the search view shows ~100000 matches, deleting resources that are shown in the search view freezes Eclipse for many minutes. With this change the freeze is only about 30 seconds. See eclipse-platform#2279
This change unifies "filter" label handling for tree/table mode in the file search, we show now that the matches are filtered in both cases. See eclipse-platform#2279
If the search view has matches for 100.000 files, it would hang forever on updating the view via F5 because it asks getMatchCount() for every element and that traverses entire result again and again. This change remembers last computed result and returns that value if there were no further changes on the search result itself. See eclipse-platform#2279
This issue is already reported here. Please close this one on Bugzilla as duplicate.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=575271
UI freezes over around 12 seconds if have a large search result in the second level tree onwards. The reason is Search View Filter viewer limit is not applied for children.
Use below snippet to generate 100k files with searchable text in it. Initiate File Search with text
text here
The text was updated successfully, but these errors were encountered: