Bug 195423

Summary:

[content assist] computes type hierarchy when filtering prefixes

Product:

[Eclipse Project] JDT

Reporter:

Markus Keller <markus.kell.r>

Component:

Text

Assignee:

JDT-Text-Inbox <jdt-text-inbox>

Status:

RESOLVED FIXED

QA Contact:

Severity:

normal

Priority:

Version:

3.3

Target Milestone:

3.4 M1

Hardware:

OS:

Windows XP

Whiteboard:

Attachments:

Description	Flags
CPU Trace	none

Description Markus Keller

2007-07-04 13:56:51 EDT

N20070704-0010

For unknown reasons, my content assist became unusably slow when I invoked it on a Composite and then started filtering the proposals:

    void m(Composite c) {
        c.|   // press Ctrl+Space here and then type "g"
    }

I took a performance trace in which I found that much of the time was burned in the type hierarchy computation triggered by ParameterGuessingProposal.computeReplacementString()

I think this has been introduced the fix for bug 188851.

Comment 1 Markus Keller

2007-07-04 14:01:16 EDT

Created attachment 73051 [details]
CPU Trace

I guess this is not the only cause of the slowness I see (I also have a heap > 180 MB with 1 open editor), but it's probably an important part.

Comment 2 Dani Megert

2007-07-10 10:04:30 EDT

- Composite is org.eclipse.swt.Composite.
- parameter guessing must be enabled

Fixed in HEAD.