Summary: | [content assist] constructor completion taking 15-20 seconds | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Pavel Samolisov <samolisov> | ||||||||||
Component: | Core | Assignee: | Ayushman Jain <amj87.iitr> | ||||||||||
Status: | NEW --- | QA Contact: | |||||||||||
Severity: | normal | ||||||||||||
Priority: | P3 | CC: | daniel_megert, markus.kell.r, Olivier_Thomann, samolisov | ||||||||||
Version: | 3.6 | Keywords: | performance | ||||||||||
Target Milestone: | --- | ||||||||||||
Hardware: | All | ||||||||||||
OS: | All | ||||||||||||
Whiteboard: | stalebug | ||||||||||||
Attachments: |
|
Description
Pavel Samolisov
2010-04-12 07:19:09 EDT
Created attachment 164552 [details]
write some letters of the classname
Created attachment 164554 [details]
Error window
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. 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. Created attachment 164688 [details]
In time stack dump
Created attachment 164689 [details]
after error stack dump
Pavel, did you get a chance to try 3.7M6? Is it better ? 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. 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. |