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 172677

Summary:	4s don't acquire writeLock when computing hints
Product:	javaee	Reporter:	Jaroslav Tulach <jtulach>
Component:	JSP	Assignee:	Marek Fukala <mfukala>
Status:	RESOLVED DUPLICATE
Severity:	blocker	CC:	ads, jlahoda
Priority:	P2
Version:	6.x
Hardware:	All
OS:	All
URL:	http://statistics.netbeans.org/exceptions/detail.do?id=158867
Issue Type:	DEFECT	Exception Reporter:	158867

Description Jaroslav Tulach 2009-09-21 12:29:45 UTC

web.jsf.editor.hints.ElCheck can block repainting of the whole system as it exclusively locks document. Probably it 
only needs read lock (e.g. Document.render(Runnable)), not runAtomic.


Build: NetBeans IDE Dev (Build 200909151512)
VM: Java HotSpot(TM) Client VM, 16.0-b06, Java(TM) SE Runtime Environment, 1.7.0-ea-b66
OS: Windows XP, 5.1, x86
User comments: 
Maximum slowness yet reported was 3719 ms, average is 3719

Comment 1 Jan Lahoda 2009-09-21 12:39:09 UTC

Use of write lock was changed to read lock in issue #172057, AFAIK. Could probably be improve by use of "micro"-locking
(locking only for short periods of time only where necessary).

Comment 2 Marek Fukala 2009-09-21 12:44:32 UTC


*** This issue has been marked as a duplicate of 172057 ***