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 183482 - Checking for external changes process takes a lot of time
Summary: Checking for external changes process takes a lot of time
Status: CLOSED DUPLICATE of bug 183201
Alias: None
Product: ide
Classification: Unclassified
Component: Performance (show other bugs)
Version: 3.x
Hardware: PC Windows XP
: P2 normal (vote)
Assignee: issues@performance
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-05 12:36 UTC by Alexandr Scherbatiy
Modified: 2011-05-25 11:40 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
IDE Thread Dump (26.61 KB, text/plain)
2010-04-05 12:36 UTC, Alexandr Scherbatiy
Details
VisuaVM-Sampler profiling snapshot (9.69 KB, application/nps)
2010-04-05 12:37 UTC, Alexandr Scherbatiy
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alexandr Scherbatiy 2010-04-05 12:36:04 UTC
NetBeans-JavaFX-Soma: #210
  Product Version         = NetBeans IDE Dev (Build 201004040201) (#e576213ffe25)
  Operating System        = Windows XP version 5.1 running on x86
  Java; VM; Vendor        = 1.6.0_15; Java HotSpot(TM) Client VM 14.1-b02; Sun Microsystems Inc.



I am editing a JavaFX project and after code editing the "Checking for external changes" task starts and takes a lot of time. The IDE becomes vary slow.

See the attached Thread Dump and the VisualVM sampler report.
Comment 1 Alexandr Scherbatiy 2010-04-05 12:36:50 UTC
Created attachment 96678 [details]
IDE Thread Dump
Comment 2 Alexandr Scherbatiy 2010-04-05 12:37:59 UTC
Created attachment 96679 [details]
VisuaVM-Sampler profiling snapshot
Comment 3 Petr Nejedly 2010-04-13 14:59:53 UTC
Known problem for the whole IDE, solved elsewhere....
Comment 4 Alexandr Scherbatiy 2010-04-14 13:22:20 UTC
Please, mark the issue duplicate of the existed or move it to the appropriate category.
Comment 5 Jaroslav Tulach 2010-04-14 17:29:54 UTC
The basic problem in the snapshot is existence of multiple logger-completion threads taking a lot of CPU. Addressed in bug 183201.

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