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 251271 - org.netbeans.core.output2.OutputDocument.stateChanged: LowPerformance took 26344 ms.
Summary: org.netbeans.core.output2.OutputDocument.stateChanged: LowPerformance took 26...
Status: RESOLVED DUPLICATE of bug 229090
Alias: None
Product: platform
Classification: Unclassified
Component: Output Window (show other bugs)
Version: 8.0
Hardware: All All
: P3 normal (vote)
Assignee: Jaroslav Havlin
URL:
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2015-03-18 23:06 UTC by Exceptions Reporter
Modified: 2015-08-17 12:08 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 216210


Attachments
nps snapshot (148.35 KB, application/nps)
2015-03-18 23:07 UTC, Exceptions Reporter
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Exceptions Reporter 2015-03-18 23:06:58 UTC
This bug was originally marked as duplicate of bug 239165, that is already resolved. This bug is still valid, so this seems to be another bug, but it might be related.

Build: NetBeans IDE 8.0.2 (Build 201411181905)
VM: Java HotSpot(TM) 64-Bit Server VM, 25.31-b07, Java(TM) SE Runtime Environment, 1.8.0_31-b13
OS: Linux

User Comments:
GUEST: I just pressed ctrl + space to get the autocomplete options and it freezed



Maximum slowness yet reported was 26344 ms, average is 26344
Comment 1 Exceptions Reporter 2015-03-18 23:07:02 UTC
Created attachment 152704 [details]
nps snapshot
Comment 2 Jaroslav Havlin 2015-08-17 12:08:18 UTC
Reports from 8.0.2 (others skipped, but probably the cause is similar):

777520 - Thread "Maven CommandLine Output Redirector" holds output lock while
         writing data to file-mapped memory, and UI is waiting for the lock.

771224 - Thread "pool-348-thread-1" (extexecution) holds output lock...

Duplicates of bug 229090.

Thank you for reporting.

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