Bug 38592 - Frozen repaint
Frozen repaint
Product: editor
Classification: Unclassified
Component: -- Other --
PC Linux
: P3 (vote)
: 4.x
Assigned To: Miloslav Metelka
Depends on:
  Show dependency treegraph
Reported: 2004-01-09 20:05 UTC by Jesse Glick
Modified: 2007-11-05 13:44 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT

Thread dump (23.23 KB, text/plain)
2004-01-09 20:06 UTC, Jesse Glick

Note You need to log in before you can comment on or make changes to this bug.
Description Jesse Glick 2004-01-09 20:05:48 UTC
No idea how to reproduce; just happened to me once
(dev-040109). I typed something and the editor
window stopped repainting. I had to close the
document and reopen it to recover. No data loss -
still offered a save dialog, did not freeze whole IDE.
Comment 1 Jesse Glick 2004-01-09 20:06:37 UTC
Created attachment 12810 [details]
Thread dump
Comment 2 Jesse Glick 2004-01-09 20:07:24 UTC
BTW is the editor module responsible for the absurd number of inactive
RequestProcessor threads?
Comment 3 Petr Nejedly 2004-01-11 21:27:45 UTC
It may or may not be the editor.
Some time ago I've added the "[Was:" info the the inactive RP, but it
wasn't enough ;-)
So I've added the class name of the last runnable to the info.

Generally, it is caused by wrong usage of RP.getDefault().
Comment 4 Martin Roskanin 2004-01-23 13:30:46 UTC
When this repaint frost happen? If immediatelly after deserialization
of the editor pane during IDE startup it should be duplicate of issue

As for inactive RP threads, it could be issue #36394

We should resolve it to NB 3.6
Assigning to Mila, he already works on issue #38993, which is similar.
Comment 5 Martin Roskanin 2004-08-18 15:29:10 UTC
I believe issue was fixed by some other integration, since there were
no similar issues entered for a long time... Please, reopen if you can
reproduce it.

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