Bug 308820 - [content assist] constructor completion taking 15-20 seconds
Summary: [content assist] constructor completion taking 15-20 seconds
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.6   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Ayushman Jain CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: performance
Depends on:
Blocks:
 
Reported: 2010-04-12 07:19 EDT by Pavel Samolisov CLA
Modified: 2022-07-10 12:02 EDT (History)
4 users (show)

See Also:


Attachments
write some letters of the classname (2.39 KB, image/png)
2010-04-12 07:20 EDT, Pavel Samolisov CLA
no flags Details
Error window (12.86 KB, image/png)
2010-04-12 07:20 EDT, Pavel Samolisov CLA
no flags Details
In time stack dump (22.24 KB, text/plain)
2010-04-13 07:35 EDT, Pavel Samolisov CLA
no flags Details
after error stack dump (16.99 KB, text/plain)
2010-04-13 07:36 EDT, Pavel Samolisov CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Pavel Samolisov CLA 2010-04-12 07:19:09 EDT
Build Identifier: I20100312-1448

In my workspace exists large set of large projects. This projects have over 5000 java classes total.

I'm writing some first letters from a classname (see first attachment) and pressing Ctrl+Space. Eclipse is thinking some time and throw the exception (see second attachment). This bug reproduce not everytime, but periodically.

Reproducible: Sometimes

Steps to Reproduce:
1. Open workspace with 5000 - 10000 classes
2. Write some first letters of the a classname
3. Press Ctrl+Spece
4. Periodically Eclipse throw exception window.
Comment 1 Pavel Samolisov CLA 2010-04-12 07:20:26 EDT
Created attachment 164552 [details]
write some letters of the classname
Comment 2 Pavel Samolisov CLA 2010-04-12 07:20:55 EDT
Created attachment 164554 [details]
Error window
Comment 3 Dani Megert CLA 2010-04-13 03:57:20 EDT
Pavel, can you check whether this happens on type completion or rather when completion a constructor i.e. after "new .... <code assist>".

How long does it take after starting completion until the dialog appears?

Please try to take some stack dumps (for guidelines on how to do this see http://wiki.eclipse.org/index.php/How_to_report_a_deadlock) and attach them here.
Comment 4 Pavel Samolisov CLA 2010-04-13 07:35:08 EDT
Dani, I have check this one. This happens when completion a constructor. 
After starting completion until the dialog appears it takes 15-20 seconds. 

I have attached jstack output for eclipse. intime.stack - stack dump that have been created in 15-20 seconds pause, after.stack - stack dump that have been created after then error window had been show.
Comment 5 Pavel Samolisov CLA 2010-04-13 07:35:55 EDT
Created attachment 164688 [details]
In time stack dump
Comment 6 Pavel Samolisov CLA 2010-04-13 07:36:36 EDT
Created attachment 164689 [details]
after error stack dump
Comment 7 Olivier Thomann CLA 2011-03-15 11:24:53 EDT
Pavel, did you get a chance to try 3.7M6?
Is it better ?
Comment 8 Eclipse Genie CLA 2020-07-09 18:33:28 EDT
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.
Comment 9 Eclipse Genie CLA 2022-07-10 12:02:11 EDT
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.