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 48320

Summary: scanning project's classpath frozen
Product: java Reporter: Marian Petras <mpetras>
Component: UnsupportedAssignee: Martin Matula <mmatula>
Status: CLOSED WORKSFORME    
Severity: blocker    
Priority: P3    
Version: 4.x   
Hardware: PC   
OS: Linux   
Issue Type: DEFECT Exception Reporter:
Attachments: screenshot of the progress dialog
full thread dump
ISE at NB shutdown.

Description Marian Petras 2004-09-01 17:12:41 UTC
I had an empty IDE and opened project "image" (the
standard NetBeans module). The IDE started to scan
the project's classpath... and suddenly it stopped
in the middle of the process (see the attached
screenshot). Apparently, the AWT event queue thrad
runs, as the IDE still gets repainted if it is
(partly or fully) obscured and then uncovered.

I will attach the full thread dump.
Comment 1 Marian Petras 2004-09-01 17:18:52 UTC
*** Issue 48322 has been marked as a duplicate of this issue. ***
Comment 2 Marian Petras 2004-09-01 17:20:50 UTC
Created attachment 17293 [details]
screenshot of the progress dialog
Comment 3 Marian Petras 2004-09-01 17:22:37 UTC
Created attachment 17294 [details]
full thread dump
Comment 4 lkishalmi 2004-10-06 14:12:40 UTC
Created attachment 18084 [details]
ISE at NB shutdown.
Comment 5 Martin Matula 2004-10-07 08:14:05 UTC
Marian, do you remember if there were any exceptions thrown to the
console before the IDE got frozen?
Comment 6 Marian Petras 2004-10-07 09:11:21 UTC
Sorry, I do not remember. If I had noticed some, I would have
mentioned them in this bug report but I am not sure.
Comment 7 Martin Matula 2004-10-07 09:18:26 UTC
Have you seen this several times, or just once when you filed this
report? I am not able to reproduce this.
Comment 8 Marian Petras 2004-10-07 10:23:51 UTC
I saw it just once.
Comment 9 Martin Matula 2004-10-25 16:12:36 UTC
Sorry, I am not able to reproduce this. We have made some
synchronization changes in BtreeDatabase and BtreeStorage which could
have fixed this. Please reopen if you see it again and attach the
whole messages.log.
Comment 10 Marian Petras 2004-10-29 14:46:42 UTC
It hasn't happend again since then. Verified.