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 38592

Summary:	Frozen repaint
Product:	editor	Reporter:	Jesse Glick <jglick>
Component:	-- Other --	Assignee:	Miloslav Metelka <mmetelka>
Status:	RESOLVED WORKSFORME
Severity:	blocker	CC:	pnejedly
Priority:	P3	Keywords:	RANDOM, THREAD
Version:	3.x
Hardware:	PC
OS:	Linux
Issue Type:	DEFECT	Exception Reporter:
Attachments:	Thread dump

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
#38993

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.