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 205739 - CPU/NB spinning at 100%
Summary: CPU/NB spinning at 100%
Status: RESOLVED DUPLICATE of bug 205241
Alias: None
Product: platform
Classification: Unclassified
Component: Filesystems (show other bugs)
Version: 7.1
Hardware: PC Windows XP
: P3 normal (vote)
Assignee: Jaroslav Tulach
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-30 19:43 UTC by err
Modified: 2011-12-05 10:19 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
thread dump while spinning (20.95 KB, application/octet-stream)
2011-11-30 19:43 UTC, err
Details
thread dump while spinning II (20.95 KB, text/plain)
2011-11-30 19:45 UTC, err
Details

Note You need to log in before you can comment on or make changes to this bug.
Description err 2011-11-30 19:43:31 UTC
Created attachment 113673 [details]
thread dump while spinning

This should have been a "slowness detected" reported problem, but I got a network time out error (probably because the CPU was at 100%).

I was working on a patch for openide.text. The file being modified was open in the IDE.
- I got the patch ready
- did "hg qnew file", on the console
- posted the patch
Then I did
- "hg qpop" on the console
this last command modified a file open in the IDE
- clicked on the file in question in the IDE

The cpu/nb started spinning. This went on for minutes until I exited the IDE. The IDE did not hang; almost all the time was in NB.

Attached is a thread dump made while spinning.


Product Version: NetBeans IDE 7.1 RC1 (Build 201111242103)
Java: 1.6.0_23; Java HotSpot(TM) Client VM 19.0-b09
System: Windows XP version 5.1 running on x86; Cp1252; en_US (nb)
Comment 1 err 2011-11-30 19:45:01 UTC
Created attachment 113674 [details]
thread dump while spinning II

Re-attach thread dump as plain text
Comment 2 Jaroslav Tulach 2011-12-05 10:19:02 UTC
Probably duplicate of bug 205241. Check your log to verify.

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