RE: [cdt-dev] huge source file and mark occurrences

["Schorn, Markus" <Markus.Schorn@xxxxxxxxxxxxx>]

To me your proposal makes sense, please file a bugzilla for it,

Markus.

---

From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Kennedy, Stephen M (Steve)
Sent: Wednesday, May 26, 2010 5:42 PM
To: CDT General developers list.
Subject: [cdt-dev] huge source file and mark occurrences
Importance: Low

I have a huge source file that was the subject of this bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=291024

 

As long as I have semantic highlighting of overloaded operators off, I've been able to browse the file with acceptable performance without resorting to scalability mode.  Recently I ran into another problem: when I click on the constructor (specifically the name after the ::), a worker thread goes off to the compute the occurrences that should be marked, e.g., part of the thread trace from jconsole:

 

...

org.eclipse.cdt.internal.core.dom.parser.cpp.semantics.CPPVisitor.getImplicitReferences(CPPVisitor.java:1850)

org.eclipse.cdt.internal.ui.search.OccurrencesFinder.performSearch(OccurrencesFinder.java:75)

org.eclipse.cdt.internal.ui.search.OccurrencesFinder.getOccurrences(OccurrencesFinder.java:103)

org.eclipse.cdt.internal.ui.editor.CEditor.updateOccurrenceAnnotations(CEditor.java:3261)

org.eclipse.cdt.internal.ui.editor.CEditor$7.selectionChanged(CEditor.java:3287)

...

 

This takes about 15 minutes to run and locks the AST in the meantime.

 

Should this be something that is also turned off when semantic highlighting of overloaded operators is also turned off, or is it something completely different?  Currently I can only disable this by checking "Disable editor live parsing" in the Scalability preferences (apart from disabling "Mark Occurrences" completely).

 

Steve Kennedy

Alcatel-Lucent