Bug 549621 - Constant Error: Notifying Selection Listeners
Summary: Constant Error: Notifying Selection Listeners
Status: NEW
Alias: None
Product: CDT
Classification: Tools
Component: cdt-indexer (show other bugs)
Version: 9.5.5   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Jonah Graham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-07-29 05:56 EDT by Stephan Oostveen CLA
Modified: 2020-12-16 08:15 EST (History)
4 users (show)

See Also:


Attachments
Eclipse log file (113.71 KB, text/x-log)
2019-07-29 05:56 EDT, Stephan Oostveen CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Stephan Oostveen CLA 2019-07-29 05:56:51 EDT
Created attachment 279416 [details]
Eclipse log file

When using Eclipse for some time the following error starts showing up: "An internal error occurred during: "Notifying selection listeners"." When this error occured once, it will keep comming in intervals of maybe 30 seconds. Attached you will find the log file.
Comment 1 Marco Stornelli CLA 2019-07-29 14:34:39 EDT
does it happen with cdt 9.8?
Comment 2 Marco Stornelli CLA 2019-07-29 14:41:20 EDT
@Nathan is it already fixed? Is it anything already seen?
Comment 3 Stephan Oostveen CLA 2019-07-30 05:16:40 EDT
(In reply to Marco Stornelli from comment #1)
> does it happen with cdt 9.8?

I'll try to reproduce the error with cdt 9.8 But it is rather hard to trigger the first occurrence of this error. But when the first error occured you get a constant stream of errors up to some point (reboot, git checkout or something else), after which it takes some time again to occur.
Comment 4 Nathan Ridge CLA 2019-07-30 17:53:27 EDT
(In reply to Marco Stornelli from comment #2)
> @Nathan is it already fixed? Is it anything already seen?

We've fixed several stack overflows in the indexer over the years, but unfortunately it's hard to tell based on the stack trace if this is the same as one that's already fixed.

Usually stack overflows like this occur due to indexer bugs that trigger infinite recursion on specific code patterns, and fixing them requires a (preferrably minimal) reproducing example so we can isolate the problematic code pattern and debug it.
Comment 5 Steven van der Schoot CLA 2020-12-16 08:15:40 EST
I'm experiencing this issue as well. A minimal example I found that triggers this: 

struct A {
    struct A;
    static constexpr auto a = A{};
}

struct A::A{
    A a{};
};

Note that this is not valid c++. Typing this code however triggers Eclipse to show the error message about every keystroke, which makes it very hard to fix the code.