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 40831 - [JDK1.5.0]RuntimeE, FNFE, IOE after CVS->Status on the Root of FS
Summary: [JDK1.5.0]RuntimeE, FNFE, IOE after CVS->Status on the Root of FS
Status: CLOSED FIXED
Alias: None
Product: platform
Classification: Unclassified
Component: Data Systems (show other bugs)
Version: 4.x
Hardware: PC Linux
: P2 blocker (vote)
Assignee: Jiri Rechtacek
URL:
Keywords: PERFORMANCE, RANDOM
Depends on:
Blocks:
 
Reported: 2004-03-08 15:16 UTC by dmladek
Modified: 2008-12-22 22:15 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
the whole ide log withe last IDE start (109.06 KB, text/plain)
2004-03-08 15:18 UTC, dmladek
Details
FullThreadDump (16.24 KB, text/plain)
2004-03-08 15:37 UTC, dmladek
Details
FullThreadDump after 1/2h of ide inactivity (only automount is bussy) (10.27 KB, text/plain)
2004-03-08 17:11 UTC, dmladek
Details
2 FTDs + .java.lang.Error + OOME + many more (48.52 KB, text/plain)
2004-03-11 11:00 UTC, dmladek
Details

Note You need to log in before you can comment on or make changes to this bug.
Description dmladek 2004-03-08 15:16:56 UTC
Product Version       = NetBeans IDE Dev (Build
200403071900)
  Operating System      = Linux version
2.4.20-18.9 running on i386
  Java; VM; Vendor      = 1.5.0-beta2; Java
HotSpot(TM) Client VM 1.5.0-beta2-b41; Sun
Microsystems Inc.
  Java Home             =
/usr/local/java/j2sdk1.5.0/jre
  System Locale; Encod. = cs_CZ; ISO-8859-2
  Home Dir; Current Dir = /usr/local/home/delphym;
/usr/local/forte/forte3/NBdev-last/netbeans/bin
  IDE Install; User Dir =
/usr/local/home/delphym/NBdev-last;
/usr/local/home/delphym/.netbeans/dev
-------------------------------------------------------------------------------


I didn't done something special. Only mount
CVS-EXT FS. And on its root I execute CVS->Status.
(This FS wasn't so huge like nb_all sources, but
wasn't also so small).

The Status Output Tab in the Editor occures and in
the console I imediately found large stacktraces
of various E.

I didn't want to pain an attention to this, but
I've realized that my IDE get terribly slow, so
I've decided to enter it into IZ and set the
priority to P2.

thanks for understanding
Comment 1 dmladek 2004-03-08 15:18:16 UTC
Created attachment 13870 [details]
the whole ide log withe last IDE start
Comment 2 dmladek 2004-03-08 15:30:57 UTC
Also I've created the ThreadDump, but it's probably useless :-/
Becasue I've done it just after I click to exit ide...
Comment 3 dmladek 2004-03-08 15:37:10 UTC
Created attachment 13873 [details]
FullThreadDump
Comment 4 dmladek 2004-03-08 17:09:23 UTC
This is realy strange :-/

Now, I've change RelMounPoint in CVS FS and got the same row of
exception stacktraces and the same Thread Dump showing for some
problems in automounter...

In the E. stacktraces there is problem with serialized commonent
related to the image: Command-line_Client.gif
which is part of another different CVS FS (which I didn't touch today)

INFORMATIONAL *********** Exception occurred ************ at Fri Mar
05 17:29:20 CET 2004
java.io.FileNotFoundException: Top component Installer-6 #005BLocally
Modified; 1#002E1#005D could not be located or loade
d from Components folder.
...
...
...
        at java.awt.EventDispatchThread.run(EventDispatchThread.java:110)
[WinSys.PersistenceManager.getTopComponentForID] Problem when
deserializing TopComponent for tcID:'Command-line_Client#002
Egif #005BLocal#005D'. Reason: Could not restore Explorer window; the
root node "" is not persistent; override Node.getHandle to fix

and the Performance problem is caused by problems in automount....



Comment 5 dmladek 2004-03-08 17:11:24 UTC
Created attachment 13878 [details]
FullThreadDump after 1/2h of ide inactivity (only automount is bussy)
Comment 6 Martin Entlicher 2004-03-08 17:27:39 UTC
The problematic exceptions seems to be:

Cannot read class: org.netbeans.core.NbMainExplorer$ExplorerTab
java.io.IOException: Could not restore Explorer window; ...
Annotation: DocListener should not throw SAXException but STOP one.

I have no idea what is the Command-line_Client.gif TopComponent, but
the setting is likely created by Window System.

Moving to core for evaluation, since I'm guessing a problem in
NbMainExplorer$ExplorerTab.

Another problem is likely the never-ending activity of Automount.
Comment 7 Marian Mirilovic 2004-03-08 20:35:31 UTC
Dan,
can you reproduce it ? ... and what about steps to reproduce on NB3.6
... with JDK1.4.2_03 ....  :(

Jirka,
please look at it, maybe deserialization of top component fails, but 
I think once again unreproducible issue from Dan ........ :(
Comment 8 dmladek 2004-03-09 23:46:34 UTC
I can't reproduce it on demand, but during a day I get into this state
many times :-( It's pretty annoying and I'd like to rise this to P2.

Comment 9 dmladek 2004-03-09 23:50:00 UTC
I'll inform you during today's work if it happens also in JDK1.4.x
(well I will use still dev build....I could verify some bugfixes.
There's no big difference between DEV and 36 so far)

Comment 10 Marian Mirilovic 2004-03-10 07:48:47 UTC
I don't think so (without priority ping-pong), there is a lot of
changes in NB3.6 now, 
so question of the day is:

Is it reproducible in NB3.6 on JDK1.4.2_03 ?

if so remove NO36 keyword and change version - then it becomes a
really problem

By the way try IDE with new userdir !!!

Thanks for cooperation ;)
Comment 11 dmladek 2004-03-10 09:28:27 UTC
OK, I'll do my best ;-)
Comment 12 Jiri Rechtacek 2004-03-10 09:47:20 UTC
The root of problem is "DocListener should not throw SAXException but
STOP one." in Folder recognizer. Reported also as issue 40729.

*** This issue has been marked as a duplicate of 40729 ***
Comment 13 dmladek 2004-03-10 11:05:39 UTC
Well, If I take in account that this is a realy duplicate (I'm not
going to comfirm it 'cause I'm not sure about it) of the bug #40729
and look at the running environment:

Bouth bugs vere rerorted on JDK1.5Beta (and happens the unix users)
The original of this one was reproted against NB 3.6BETA !!!!
And I'm reporting it against NB DEV.

Thus I'm more convincted that it is also in branch: NB36

So the question of the day is:
Is it realy JDK1.5 specific?  (thus I'm continue my work on yesturday
DEV running on JDK1.4.x)
Comment 14 dmladek 2004-03-10 15:06:52 UTC
Removing JDK_SPECIFIC kw. It's happening on jdk1.4.2_03 too.
Comment 15 dmladek 2004-03-10 15:18:43 UTC
I've spoke with Marian and he still think it is jdk1.5 specific and
doeasn't accept my reproduction because I'm alwas using my old user
dir and once run on jdk1.5 and then on jdk1.4

Also removing NO36 kw 'cause originaly it was reproted on the NB36
Beta branch. Also it is in current DEV. Thus I think it must be in
NB36 branch too.
Comment 16 dmladek 2004-03-10 17:02:43 UTC
This is not duplicate.
See Additional Comments From Trung Duc Tran 2004-03-10 08:17 PST 

>dmladek, don't mix things together.  This bug is about NPE when
>changing  projects.  What your thread dumps have to do with that?

Comment 17 dmladek 2004-03-11 10:56:41 UTC
Still the same (maybe worse ->OOME)....trying on:
  Product Version       = NetBeans IDE Dev (Build 200403102255)
  Operating System      = Linux version 2.4.20-18.9 running on i386
  Java; VM; Vendor      = 1.4.2_03; Java HotSpot(TM) Client VM
1.4.2_03-b02; Sun Microsystems Inc.
  Java Home             = /usr/local/java/j2sdk1.4.2_03/jre
  System Locale; Encod. = cs_CZ; ISO-8859-2
  Home Dir; Current Dir = /usr/local/home/delphym;
/usr/local/forte/forte3/NBdev-last/netbeans/bin
  IDE Install; User Dir = /usr/local/home/delphym/NBdev-last;
/usr/local/home/delphym/.netbeans/dev
-------------------------------------------------------------------------------

After IDE started up, I several times loged in and loged out from CVS
FSs and also invoked customizers one them.

Then CPU, again, get 99% of usage. I've created ThreadDumps which I'm
going to attache.

Attachment include all outputs from console since ide starts.
After first TreadDump there's occured OOME and others stacktraces
(java.lang.Error)


Comment 18 dmladek 2004-03-11 11:00:09 UTC
Created attachment 13939 [details]
2 FTDs + .java.lang.Error + OOME + many more
Comment 19 Jiri Rechtacek 2004-03-12 11:07:15 UTC
Dane, could you reproduce with today's build? I guess it'll work for
you. Thanks
Comment 20 Jiri Rechtacek 2004-03-24 10:05:42 UTC
No response for long time. I assume the fixes issue 40729 also fix this.
Comment 21 dmladek 2004-07-27 16:07:37 UTC
It's OK now. (sorry for late response)