Previously, the Eclipse IDE shell script editor loaded the whole manual page for display as a hover tip when the user hovered the mouse cursor over a command. As a consequence, hovering the mouse cursor over a command with a large manual page in the shell script file editor made the Eclipse IDE unresponsive. The hover help mechanism has been restricted to load only up to 10 kB of manual page data, and extended to advise the user to use the "Show Man Page" command in a dedicated view when the manual page data is truncated. As a result, the Eclipse IDE stays responsive in the described scenario.
Created attachment 1315997[details]
example script
Description of problem:
Hover on command in script freezes Eclipse
Whenever I click or hover on a command in the Eclipse Shell Script Editor (DLTK ), the entire Eclipse UI freezes. If the command has a long man page, e.g. "cmake", the freeze lasts upward of 10 minutes.
Version-Release number of selected component (if applicable):
rh-eclipse46:
Eclipse version:
Version: Neon.3 (4.6.3)
Build id: X20170404-1006
DLTK version:
Eclipse Dynamic Languages Toolkit - Core Frameworks
Version: 5.7.1.201703310856
Build id: @build@
How reproducible:
Always
Steps to Reproduce:
1. Create a general project.
2. Create a new script (.sh file).
3. Open the new script.
4. Write "cmake"
5. Hover on "cmake" or click on it.
Or:
1. Import project from attached archive.
2. Open script "someScript.sh".
3. Hover on "cmake" or click on it.
Actual results:
IDE gets stuck and does not respond.
Expected results:
IDE should show tip
Additional info:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=520607
Hi Piyush,
I plan to address this for the upcoming release of rh-eclipse47 collection during the next few weeks, then we can probably think about back-porting a fix rh-eclipse46.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2017:3129