Community
Participate
Working Groups
Created attachment 288022 [details] Sometimes，the code tip is too slow Sometimes，the code tip is too slow and an error occurred.
When I open the code hint, this problem will appear. It freezes and does not respond.
Some ideas to mitigate the delay: I guess it very much depends on the detailed configuration of context assist in the preferences. In my experience e.g. subword matches can make it slow, and other toggles, too. Play around with it. I also set the auto activation delay to 0ms, which seems to speed up the proposals. I'm not exactly sure how the effect plays out, but tailoring the type filters to your needs (and thus reducing the number of possible matches) might help, too. Sometimes it seems to help to rebuild the index, but the effect seems to vanish soon. Another recent discovery for me was the "derived" setting of folders for everything that is generated e.g. during a build. Setting folders like maven's target to "derived" makes Eclipse ignore the contents of the folders for search actions, and thus might speed up the content assist, too. There's helpful little plugin called AutoDeriv that even automates the "derived" setting based on file/folder name patterns. As a workaround for the error message in your video you might play with the settings in the "UI Freeze Monitoring" section of the preferences.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
