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 164932 - IDE unresponsive, ParserManager.parse called in AWT event thread
Summary: IDE unresponsive, ParserManager.parse called in AWT event thread
Status: CLOSED INCOMPLETE
Alias: None
Product: qa
Classification: Unclassified
Component: Code (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: issues@qa
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-12 12:51 UTC by Vojtech Sigler
Modified: 2011-02-17 09:31 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Thread dump (14.09 KB, application/octet-stream)
2009-05-12 14:01 UTC, Vojtech Sigler
Details
Hopefully the correct thread dump (40.22 KB, text/plain)
2009-05-21 12:13 UTC, Vojtech Sigler
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Vojtech Sigler 2009-05-12 12:51:08 UTC
A process (scanning source code I would expect) is being called in AWT event thread causing the ide to become
unresponsive (until the process finishes). Also, as a consequence, the window is not refreshed (redrawn) during this time.

Steps to reproduce:

1. Start netbeans (with let's say 10 java projects open, enough to keep "Scanning projects" on for a while)
2. Select a project (one of the first, so that after it is scanned, there are more projects to scan) and open a java
class in that project

Expected behavior: The java file opened immediately.

Observed behavior: The ide becomes unresponsive and the window is not redrawn until all projects are scanned. The file
is opened only after the scanning is complete.

Message log says:
WARNING [org.netbeans.modules.parsing.impl.TaskProcessor]: ParserManager.parse called in AWT event thread by:
org.netbeans.api.java.source.SourceUtils.getMainClasses(SourceUtils.java:775)
Comment 1 Rastislav Komara 2009-05-12 13:43:36 UTC
Please provide thread dump and build number of used build. We already fix one similar issue.
Comment 2 Vojtech Sigler 2009-05-12 14:01:41 UTC
Created attachment 81962 [details]
Thread dump
Comment 3 Vojtech Sigler 2009-05-12 14:03:58 UTC
I'm sorry, I forgot to attach thread dump and the build number.

Build no.:  200905120201
Comment 4 Vitezslav Stejskal 2009-05-12 15:43:50 UTC
Please attach the threaddump, not the profiler snapshot. Profiler snapshots won't show if there was a deadlock or what
each thread was doing at a given point in time. Thanks

http://wiki.netbeans.org/GenerateThreadDump
Comment 5 Vojtech Sigler 2009-05-21 12:13:31 UTC
Created attachment 82540 [details]
Hopefully the correct thread dump
Comment 6 _ tboudreau 2009-07-25 04:45:16 UTC
This issue appears to actually be in the contrib/jemmysupport module, not the Java module;  a workaround (if you are not
developing NB platform apps and really using Jemmy) would be to disable that module;  jemmysupport is not part of the
IDE and must have been downloaded from the update center.

org.netbeans.modules.jemmysupport.runinternally.RunInternallyAction.getSelectedMainClass(RunInternallyAction.java:258)
	at org.netbeans.modules.jemmysupport.runinternally.RunInternallyAction.enable(RunInternallyAction.java:140)

Also, it appears in source that org.netbeans.modules.jemmysupport.runinternally.RunInternallyAction no longer exists, so
probably this bug can be closed.
Comment 7 Jan Lahoda 2009-08-20 10:00:30 UTC
Reassigning all moonko's java/source bugs to myself.
Comment 8 Tomas Zezula 2009-09-07 15:34:40 UTC
The same evaluation as Tim above.