This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 199050 - CodeCompletion took 13495 ms.
Summary: CodeCompletion took 13495 ms.
Status: RESOLVED DUPLICATE of bug 231108
Alias: None
Product: php
Classification: Unclassified
Component: Editor (show other bugs)
Version: 7.0
Hardware: All All
: P3 normal (vote)
Assignee: Ondrej Brejla
URL:
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2011-05-31 15:12 UTC by felipbou
Modified: 2013-06-12 08:40 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 178997


Attachments
nps snapshot (200.05 KB, application/nps)
2011-05-31 15:12 UTC, felipbou
Details

Note You need to log in before you can comment on or make changes to this bug.
Description felipbou 2011-05-31 15:12:11 UTC
Build: NetBeans IDE Dev (Build 201105300401)
VM: Java HotSpot(TM) 64-Bit Server VM, 14.1-b02-90, Java(TM) SE Runtime Environment, 1.6.0_15-b03-219
OS: Mac OS X

User Comments:
felipbou: Writing php code

GUEST: code completion in current file

DahliaNoir: Scanning projects is endless for only ONE project
Can't edit formatting code properties



Maximum slowness yet reported was 13495 ms, average is 6742
Comment 1 felipbou 2011-05-31 15:12:20 UTC
Created attachment 108628 [details]
nps snapshot
Comment 2 Marek Fukala 2011-06-02 10:53:28 UTC
HtmlCompletionQuery just submits a task to ParserManager.parse(...) but the parsing infrastructure is blocked by the RepositoryUpdater. I do not see anything wrong on this since the completion shows the "Scanning in progress" message.
Comment 3 Petr Jiricka 2011-06-22 15:10:21 UTC
Right, this happened to me as well - I would say the slowness detection infrastructure should not report cases when scan is in progress.
Comment 4 Petah 2013-06-11 22:43:54 UTC
This is happening for me after the scan is finished.
Comment 5 Marek Fukala 2013-06-12 08:21:28 UTC
The parsing thread is busy with PHP semantic analyzer which does some slow URLs resolving.

1) the semantic analyzer shouldn't be so slow
2) as the html completion does run a UserTask via ParserManager.parse(source, <UserTask>) this call should have much higher priority than any semantic analysis. I'm not sure about the parsing api internals but I'd expect all the lower priority tasks being cancelled when one runs the UserTask. My question is - does the PHP semantic analyzer properly react on the task being cancelled?
Comment 6 Ondrej Brejla 2013-06-12 08:40:15 UTC
Not all reports are php semantic highlighter related. A lot of them is about slow getFileAttributes, lot of them are common when one has really big project where a lot of inheritance is used, a lot of them have already been fixed (resolving of deprecated invocations) and bunch of them are toooo old or too small.So I'll mark it as a duplicate of issue #231108, because most of the latest are of the same problem.

*** This bug has been marked as a duplicate of bug 231108 ***