Summary: | UI freeze in HyperlinkDetectorDelegate.detectHyperlinks | ||
---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Lars Vogel <Lars.Vogel> |
Component: | UI | Assignee: | Platform-UI-Inbox <Platform-UI-Inbox> |
Status: | NEW --- | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | CC: | Lars.Vogel, michael.keppler, mistria, paul-eclipse |
Version: | 4.14 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Linux | ||
Whiteboard: |
Description
Lars Vogel
2019-10-29 08:43:06 EDT
Looking at the code in https://git.eclipse.org/c/lsp4e/lsp4e.git/tree/org.eclipse.lsp4e/src/org/eclipse/lsp4e/operations/declaration/OpenDeclarationHyperlinkDetector.java#n90 I assume that lsp4e waits up to 500 msecs for all the language servers to complete that operation. If your UI freeze reporting is set to a threshold lower than 500 msecs you probably see an issue for each invocation that reaches the 500 msecs limit. However, I might be completely wrong with this analysis, since I have never used CompletableFutures yet. |