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 57966 - Consuming CPU while working in JSP projects
Summary: Consuming CPU while working in JSP projects
Status: CLOSED INVALID
Alias: None
Product: javaee
Classification: Unclassified
Component: JSP (show other bugs)
Version: 4.x
Hardware: All All
: P3 blocker (vote)
Assignee: Petr Pisl
URL:
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2005-04-17 18:51 UTC by sokkary
Modified: 2006-03-24 13:00 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description sokkary 2005-04-17 18:51:53 UTC
while I'm working with netbeans 4.1 beta on windows XP. The netBeans consumes
90-99 of CPU usage ?!!!!!!!

this is happened many times while working in many JSP projects Using TomCat as
my server.

I just wanted to issue this problem as I'm working with netbeans and I respect
this IDE.
thx
Comment 1 _ rkubacki 2005-04-18 13:37:37 UTC
reassigning
Comment 2 zikmund 2005-04-18 13:54:36 UTC
Does it happen to you while you edit JSP files? There were some fixes of
processor usage while editing JSPs (see issue 55525, issue 55628 and issue 55719).

Could you please try your project in latest Q-build? If your problem still
remains, please describe under which condition does it happen. Thanks!
Comment 3 Petr Pisl 2005-04-18 14:02:06 UTC
Hi,

Karel mark this issue as INCOMPLETE, because we need more info.
Which build number?
In which situation the ide consumes CPU? During editing jsp files or during java
files.
Which configuration is your machine?
Comment 4 zikmund 2005-05-12 18:40:28 UTC
No info from report - closing as Invalid.
Feel free to reopen with requested information, thanks.
Comment 5 Jiri Kovalsky 2006-02-28 11:35:09 UTC
Verifying as invalid report. Please note that we really need more information
from you to fix this. In case you spot the same performance problem, try to
generate a thread dump
http://qa.netbeans.org/bugzilla/generating-thread-dumps.html and attach it here
with further description of what you were doing. Thanks for your cooperation !