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.
Product Version = NetBeans IDE Dev (Build 200210250100) IDE Versioning = IDE/1 spec=3.16 impl=200210250100 Operating System = Linux version 2.4.18 running on i386 Java; VM; Vendor = 1.4.1_01; Java HotSpot(TM) Client VM 1.4.1_01-b01; Sun Microsystems Inc. Java Home = /usr/java/j2sdk1.4/sun/jdk1.4.1_01/jre System Locale; Encod. = cs_CZ; ISO-8859-2 Home Dir; Current Dir = /home.local/danielm; /DISKS/storage3/forte/NBdev-last/netbeans/bin IDE Install; User Dir = /home.local/danielm/NBdev-last; /home.local/danielm/.netbeans/dev ------------------------------------------------------------------------------- I played with windows in my IDE (SDI mode): un/docking them. Suddenly I (my PC) was almost overflowen with unfinished stacktraces of Exceptions... see part of it attached as stacktrace
Created attachment 7789 [details] neverending stacktraces
It seems to me that it is bug in JDK. We just call JTabbedPane.getBoundsAt(). Peter please can you check it?
BoxLayout has got into inconsistent state (partially intited). From the code it is not possible to see how it could happen. To the log you posted. What happened before the NPE's? Those aren't interesting enough, just a consequence showing BoxLayout is in inconsistent state, but the problem is how it got into that. I suppose there could have been some exception thrown before, when initialization of the BoxLayout was in progress, left it just partially inited.
Adding a keyword:RANDOM 'cause it's unreproductable
I was looking into my ide.log and attaching it whole from my last start when problem occured. Realy there's nothing before NPE:-/ And my latest steps which I was doing before were: I have a testing class (which I could also attach here), which invokes Explorer, switchs into FileSystems TAB, then finds a JavaCVS FS node and invokes VCS Groups dialog from Main->Versioning menu, which is then verified and docked into explorer via Main->Window->Dock View Into -> Explorer ->Center and the same is for Versioning Explorer... My tests got little bit into troubles with one of Editor's TAB where I had opened VersioningExplorerOperator and wchi was selected instead of Versioning Window ... (that is what I was adjusting and solving this problem).... So repeatedly I made changes, compiled and executed, etc... Sometimes I killed the running process (which is not sometimes easy if NetBeans is rulled via GUI and you're trying be stronger the n automat:) and then it happens....
Created attachment 7790 [details] my full ide.log
Hm, that's complicated. Anyway the Boxlayout is connected to the toolbar which is shown in the source editor component. I don't know how it is implemented and where (java or editor?), and if affects this issue. But assigning there so the guys take a look on it too.
The toolbar is realized by Editor module AFAIK -> reassigning
I've found JDK issue http://developer.java.sun.com/developer/bugParade/bugs/4411096.html that is the same issue (xTotal or yTotal are null) just entered against jdk1.3. It's true that the toolbar instances are shared among the opened files with the same corresponding mimetype and therefore they are dynamically added/removed to/from the existing components which is somewhat unusual. However the operations are done properly in the AWT thread so there should be no ill behavior seen. I'll update the JDK bug with link to this issue and then close this issue.
I've updated the JDK issue. Closing as INVALID.
OK, agree with invalid