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 228219 - Periodic wait-cursor while developing HTML-5 app w/Chrome integration
Summary: Periodic wait-cursor while developing HTML-5 app w/Chrome integration
Status: RESOLVED FIXED
Alias: None
Product: web
Classification: Unclassified
Component: HTML Navigator (show other bugs)
Version: 7.3
Hardware: PC Windows 7 x64
: P2 normal (vote)
Assignee: Jan Becicka
URL:
Keywords:
Depends on: 229260
Blocks:
  Show dependency tree
 
Reported: 2013-04-03 18:16 UTC by jason3421
Modified: 2013-05-02 14:09 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Sample taken during the wait-cursor period (271.70 KB, application/octet-stream)
2013-04-03 18:16 UTC, jason3421
Details
Netbeans taking all 8 cores (13.99 KB, application/octet-stream)
2013-04-08 17:51 UTC, jason3421
Details

Note You need to log in before you can comment on or make changes to this bug.
Description jason3421 2013-04-03 18:16:46 UTC
Created attachment 133285 [details]
Sample taken during the wait-cursor period

I have 8 cores and I keep netbeans up-to-date. I'm at Build 201302132200 with JAVA 1.7_15 x64. Every since today's update I'm seeing netbeans periodically put up the wait cursor for about 10-25 seconds and take up between 1 and 4 of my 8 cores. I'll attach a self-samples to this issue. I'll also try wiping my netbeans cache and seeing if that helps.
Comment 1 Petr Cyhelsky 2013-04-04 08:46:26 UTC
reassigning to platform/explorer
Comment 2 jason3421 2013-04-08 17:51:31 UTC
Created attachment 133379 [details]
Netbeans taking all 8 cores

I've had to shut netbeans down and restart it often. Wiping the might have helped, but it didn't fix the issue. I'm attaching another selfsampler session during a period where netbeans took over virtually 100% of all 8 of my CPU cores and wasn't responsive.
Comment 3 Vladimir Riha 2013-04-10 12:30:48 UTC
I guess this is more likely Navigator related?

Reportert, could you please specify in which file are you typing and if Navigator window changes during this action and if so, does closing Navigator help? Thanks
Comment 4 Marek Fukala 2013-04-10 16:10:54 UTC
yes, it's html.navigator.HtmlElementNode.updateRecursively()
Comment 5 jason3421 2013-04-11 01:32:03 UTC
I've spent a couple of hours on this project today and have not seen this behavior repro as of yet. I'll be working on it more tomorrow. What I remember about this is that it only happened when netbeans was running my HTML/javascript app with chrome integration and even closing netbeans by using the X wasn't very responsive. If this happens again I'll try to take a few screenshots or record a short video - and try closing navigator.