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.
| Summary: | Internal websocket server eats 100% CPU | ||
|---|---|---|---|
| Product: | ide | Reporter: | Petr Jiricka <pjiricka> |
| Component: | Extbrowser | Assignee: | Denis Anisimov <ads> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | Keywords: | PERFORMANCE |
| Priority: | P2 | ||
| Version: | 7.2 | ||
| Hardware: | PC | ||
| OS: | Mac OS X | ||
| Issue Type: | DEFECT | Exception Reporter: | |
| Attachments: |
Profiler snapshot
Screenshot of the snapshot |
||
Created attachment 115992 [details]
Screenshot of the snapshot
Why do you think the problem is websocket server ? I see two GF logview processes that also eat processor. Socket server spend time inside of JDK (NIO) calls : Selector.select() SocketChanel.read() Both methods has no relation to WS server implementation logic. They are mapped into native OS network calls. At the same time mentioned GF calls are InputStream read() methods which are blocking IO operations. So it seems this is combination of some network influence issue with main blocking IO operation in GF code. Are there exact steps to reproduce ? OK, it seems I got it. The CPU is occupied because of "while" cycle in the main server code. Socket channel is requested to close in the cycle but it's not closed and as result it is not removed from available keys. So the cycle works infinitely without sleep. web-main#c07cce1921a1 Integrated into 'main-golden', will be available in build *201209031048* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/c07cce1921a1 User: Denis Anisimov <ads@netbeans.org> Log: Fix for BZ#208711 - Internal websocket server eats 100% CPU |
Created attachment 115991 [details] Profiler snapshot Build from the Easel branch - after connecting the browser to the IDE, the embedded websocket server eats 100% of CPU - see the attached profiler snapshot.