Please use the Apache issue tracking system for new NetBeans issues ( !!
Bug 223984 - Provide diagnostics for tasks running under document's read/write lock for a long time
Provide diagnostics for tasks running under document's read/write lock for a ...
Product: editor
Classification: Unclassified
Component: Painting & Printing
PC All
: P3 (vote)
: 7.3
Assigned To: Miloslav Metelka
Depends on:
Blocks: 221658
  Show dependency treegraph
Reported: 2012-12-18 14:34 UTC by Miloslav Metelka
Modified: 2016-07-07 07:29 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT


Note You need to log in before you can comment on or make changes to this bug.
Description Miloslav Metelka 2012-12-18 14:34:00 UTC
As pointed out by Vladimir there can be tasks that traverse document's content (e.g. a lexer's tokens) and take several hundreds of ms. Such task may block document modifications. We should establish a mechanism for identifying such tasks.
Comment 1 Miloslav Metelka 2012-12-18 15:05:15 UTC
Although AbstractDocument.readLock() and writeLock() are protected final, the render() and runAtomic() could be enhanced with the execution time checking functionality.
I propose to support configurable thresholds e.g.


Exceeding the thresholds would report the problematic thread's stack. What do you think?
Comment 2 Vladimir Voskresensky 2012-12-18 15:26:08 UTC
Mila, Configurable properties are great. We'll run our responsiveness test with different values then.
Comment 3 Martin Balin 2016-07-07 07:29:05 UTC
This old bug may not be relevant anymore. If you can still reproduce it in 8.2 development builds please reopen this issue.

Thanks for your cooperation,
NetBeans IDE 8.2 Release Boss

By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2014, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo