Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 333539

Summary:	AbstractScope.getSingleElement slow
Product:	[Modeling] TMF	Reporter:	Mark Christiaens <mark.g.j.christiaens>
Component:	Xtext	Assignee:	Project Inbox <tmf.xtext-inbox>
Status:	CLOSED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	mark.g.j.christiaens, sebastian.zarnekow
Version:	2.0.0	Flags:	sebastian.zarnekow: indigo+
Target Milestone:	M5
Hardware:	PC
OS:	Linux
Whiteboard:

Description Mark Christiaens

2011-01-05 04:38:24 EST

Build Identifier: 20100917-0705

Building a project with > 800 files.  Most of them are small but a couple are big (~ 2 MB).  Had to terminate the building after a couple of hours.  Using my profiler, a lot of time (90% and more) is spent in AbstractScope.getSingleElement, getElements and Google iterators.  It seems that it has something to do with the attempt to find the shadowed elements in a scope.  I don't quite understand the idea behind the ISelector and shadowing concepts so I can't give a good suggestion for a fix.  

I'm using the M4 build.

Reproducible: Always

Comment 1 Sebastian Zarnekow

2011-01-05 04:43:38 EST

Could you verify that the problem is still present if you take the latest sources from the repository?

Comment 2 Mark Christiaens

2011-01-05 05:26:58 EST

(In reply to comment #1)
> Could you verify that the problem is still present if you take the latest
> sources from the repository?

I'm a bit reluctant to really track the HEAD.  I see that there's still a lot of API change and it makes it hard for me to do some actual development.  But, if you think that the HEAD is at the moment in a sufficiently stable state for me to test this, I could make an effort.

Comment 3 Sebastian Zarnekow

2011-01-05 05:39:17 EST

Mark,

you are right there is a lot of stuff going on in the repo. However, this week we try to clean up some APIs so I think mid January should be a good time to try it again. I'll keep you posted.

Regards,
Sebastian

Comment 4 Sebastian Zarnekow

2011-01-30 09:25:08 EST

I consider this one to be fixed. Please reopen if the problem is still present.

Comment 5 Karsten Thoms

2017-09-19 17:35:31 EDT

Closing all bugs that were set to RESOLVED before Neon.0

Comment 6 Karsten Thoms

2017-09-19 17:46:27 EDT

Closing all bugs that were set to RESOLVED before Neon.0