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 49546 - application locking up when I try to close the application or close the library window
Summary: application locking up when I try to close the application or close the libra...
Status: RESOLVED FIXED
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 4.x
Hardware: PC Linux
: P3 blocker (vote)
Assignee: issues@java
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-09-24 21:45 UTC by ghyde
Modified: 2007-09-26 09:14 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
messages log file (301.36 KB, text/plain)
2004-09-27 16:14 UTC, ghyde
Details
another messages log file (399.39 KB, text/plain)
2004-09-27 16:15 UTC, ghyde
Details

Note You need to log in before you can comment on or make changes to this bug.
Description ghyde 2004-09-24 21:45:47 UTC
I'm using the 200409100847 qbuild of the 4.0
version and every time I close the window for the
library editing or when I try to close the entire
app (either by clicking on the red X in the upper
right corner or by going to File-->Exit) the
entire application locks up and I have to go into
my processes and kill the netbeans process. I'm
running Suse 9.1 with java 1.4.2_05.
Comment 1 pfelenda 2004-09-27 15:20:27 UTC
Could you please attach the messages.log file. It is in netbeans
userdir directory in directory var/log/?

Are there steps to reproduce ?
What do you do before ide comes in this state ?
Thanks
Comment 2 ghyde 2004-09-27 15:32:57 UTC
After some more testing to see how reproducable the issue is I found a
few more things. The application does lock up completely but it's not
permanent. It seems that it's doing some kind of huge state saving and
is just taking a very long time (we're talking on the order of
minutes, not seconds), To find this out I got the usual lock up but
didnt' kill it after a few seconds to try looking at some of my system
resources to see what was happening and after a period of time (can't
say exactly how long, it was minutes at least) it finally closed and
subsequent openings and closings were much quicker (on the order of
normal applications). From what I can tell it seems that this is from
the initial startup of the app after install when it reads in all the
java base stuff plus any other libraries you guys have setup by
default. I would say it may be my machine but I'm running a P4 3.06
GHz with 1GB of memory. I do not believe I saw this issue when I was
using the base beta version. Let me know if I can be of more help.
Comment 3 pfelenda 2004-09-27 16:12:28 UTC
There should help the messages.log file.
Please add it as attachment.
Thanks
Comment 4 ghyde 2004-09-27 16:14:58 UTC
Created attachment 17893 [details]
messages log file
Comment 5 ghyde 2004-09-27 16:15:23 UTC
Created attachment 17894 [details]
another messages log file
Comment 6 ghyde 2004-09-27 16:16:07 UTC
I have 2 of the files with the same date so I'm not exactly sure which
one is the one you need so I attached both. messages.log.1 is newer.
Comment 7 pfelenda 2004-09-27 16:39:35 UTC
There are two exceptions in log files:

1)
javax.enterprise.deploy.spi.exceptions.ConfigurationException
	at
org.netbeans.modules.j2ee.deployment.config.ConfigDataObject.getStorage(ConfigDataObject.java:197)

2)
java.io.FileNotFoundException:
/home/ghyde/.netbeans/dev/var/cache/mdrstorage/org-netbeans-java/0.60/f74c4cc48ea4926967f50faefcbc158bb3a861735ojectsCarrrtasrc14.cdx
(No such file or directory)
	at java.io.FileInputStream.open(Native Method)
	at java.io.FileInputStream.<init>(FileInputStream.java:106)
	at
org.netbeans.modules.javacore.ClassIndex.loadIndexFrom(ClassIndex.java:273)


-----------

 It seems that the IDE can't finds some important files.

Reassigning to javacore module.
Comment 8 Martin Matula 2004-10-07 09:34:12 UTC
The long delay after closing netbeans was fixed by introducing a
progress bar.
The FileNotFound exception that Petr extracted from the log is just
informational.
Comment 9 Quality Engineering 2007-09-20 12:04:33 UTC
Reorganization of java component