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: | 5s in output2.AbstractLines.actionPerformed() | ||
---|---|---|---|
Product: | platform | Reporter: | Exceptions Reporter <exceptions_reporter> |
Component: | Output Window | Assignee: | Jaroslav Havlin <jhavlin> |
Status: | NEW --- | ||
Severity: | normal | CC: | AlainD, aquaglia, davti, henda, hideraldo.mello, hmichel, janario, javydreamercsw, jglick, jmichelberger, jtulach, kiroff, man_k3561, mklaehn, ovrabec, rjdkolb, rodrigorsantos, rptmaestro, squib, tusharvjoshi, vnhjdh |
Priority: | P3 | Keywords: | PERFORMANCE |
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | 160254 |
Attachments: | nps snapshot |
Description
Exceptions Reporter
2009-12-22 05:23:46 UTC
Created attachment 92852 [details]
nps snapshot
Probably it shall be easy to move most of the action outside of AWT thread... Very similar to bug #178497. AWT is waiting for a lock that is held by the write thread. (In reply to comment #2) > Probably it shall be easy to move most of the action outside of AWT thread... Thanks Jaroslav, can you explain what you mean (or indicates me appropriate doc), please. I am using this architecture since 1996, and it's the first time I see a similar issue. However, the only thing that changed was an upgrade from Window7 to Window8. Thanks Martin, You mean: The Netbeans UI (not the one I am coding and testing) is locked because it waits for the output to finish writing? As it was seldom the case with W7 (three weeks ago), and the only difference I can see is a decrease in the available RAM, do you think a RAM extension will solve the issue? Note: I do not thing the issue is specific to Netbeans, but it is the most sensitive product, may be because I spend more 10hrs/day on it. AlainD *** Bug 245246 has been marked as a duplicate of this bug. *** |