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 226081 - NetBeans is no longer usable
Summary: NetBeans is no longer usable
Status: RESOLVED DUPLICATE of bug 225603
Alias: None
Product: php
Classification: Unclassified
Component: Editor (show other bugs)
Version: 7.4
Hardware: All All
: P3 normal (vote)
Assignee: Ondrej Brejla
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-02-13 18:22 UTC by rozwell
Modified: 2013-02-15 02:46 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
slowness snapshot (3.67 MB, application/octet-stream)
2013-02-13 19:16 UTC, rozwell
Details

Note You need to log in before you can comment on or make changes to this bug.
Description rozwell 2013-02-13 18:22:13 UTC
For many Hudson builds NetBeans is unusable with projects it used to work fine.
Basically everything gets extremely slow and even regular typing chokes. Simple autocompletion is consuming around 2-3 of 8 cores. And that's after freshly opened projects with clean cache.

Tried oracle-java 6, 7 & 8 with similar/same results.
Last checked on build 6058 from http://bertram.netbeans.org:8080/job/PHP-build/

Hardware: Intel i7-2670QM, 8GB memory, SSD disk

p.s.
Probably around 100 builds ago it was ok.
Comment 1 Ondrej Brejla 2013-02-13 18:37:06 UTC
Maybe it's caused by merged PHP features branch (if the slowness is caused only by PHP modules). Probably it's caused by "deprecation" support in semantic highlighting. Can you provide us some profiling snapshots caught during slowness and attach them here? [1] Without that information, we can't locate the exact cause of slowness. Thanks in advance.

[1] http://wiki.netbeans.org/FaqProfileMeNow
Comment 2 rozwell 2013-02-13 19:16:22 UTC
Created attachment 131360 [details]
slowness snapshot

Firstly I did some basic operations and then I tried to go to the class declaration by clicking on the class name (it was in the same file).
It eventually worked but after many clicks.
Comment 3 rozwell 2013-02-13 19:22:31 UTC
I didn't install Java Profiler plugin but used built in profiler. Is this snapshot fine?
Comment 4 Ondrej Brejla 2013-02-13 19:25:44 UTC
Thanks! It's exactly what I thought :) Semantic highlighting is really slow...because of checking of deprecated elements. Thanks for that!

I have another issue opened for this, so making this a duplicate. There is another user who helps me with testing too, so you can participate. It helps me a lot :) Thanks to both of you.

*** This bug has been marked as a duplicate of bug 225603 ***
Comment 5 rozwell 2013-02-13 19:39:01 UTC
Not a problem ;)
Good luck with the fix!