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.
Summary: | AIOOBE during opening a new project | ||
---|---|---|---|
Product: | platform | Reporter: | dschultheis <dschultheis> |
Component: | Window System | Assignee: | Milos Kleint <mkleint> |
Status: | RESOLVED FIXED | ||
Severity: | blocker | CC: | blaha, dsimonek, juhrik, mmirilovic, mschovanek, pattyd19, petersl, phrebejk |
Priority: | P2 | ||
Version: | 5.x | ||
Hardware: | Macintosh | ||
OS: | Mac OS X | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: |
message.log
messages.log of last version from 23.08.2005 Log file for previous comment textual diff of the suggested change. 6.0 trunk projectui jar with custom patch applied. the 5.5 dev version of the projectui module with the patch applied. Screen shot of issue Screen shot of issue w/ Release 2 |
Description
dschultheis
2005-07-05 13:39:54 UTC
Can you be more specific please? Can you provide more information about version of jdk? Is this problem reproducible? Does this problem occur for empty userdir? System Resorces: MacOSX 10.4.2, JDK 1.4.2 This Problem occur if I try to create a new Project. During creating pop up an error dialog with ArrayIndexOutOfBoundsException. This behavior is allways reproducible. Are you using the latest daily builds. I check the code from the attached exception and it shouldn't be possible to get here in the latest builds. Since it seems that you doesn't have any NetBeans platform defined - not possible, since always is at least the default available (the one you are just running). If you are still able to reproduce with the clean userdir and latest dev build feel free to reopen, thanks. I have downloaded he latest daily version and have cleaned my userdir. After that I started netbeans and opened new project. After that I get the folow exception: java.lang.ArrayIndexOutOfBoundsException: 1 at java.awt.Container.createHierarchyEvents(Container.java:934) at java.awt.Container.createHierarchyEvents(Container.java:934) at java.awt.Container.createHierarchyEvents(Container.java:934) at java.awt.Container.createHierarchyEvents(Container.java:934) at java.awt.Container.createHierarchyEvents(Container.java:934) at java.awt.Container.createHierarchyEvents(Container.java:934) at java.awt.Container.createHierarchyEvents(Container.java:934) at java.awt.Dialog.conditionalShow(Dialog.java:463) at java.awt.Dialog.show(Dialog.java:524) at org.netbeans.core.windows.services.NbPresenter.superShow(NbPresenter.java:800) at org.netbeans.core.windows.services.NbPresenter.doShow(NbPresenter.java:843) at org.netbeans.core.windows.services.NbPresenter.run(NbPresenter.java:831) at org.openide.util.Mutex$1.run(Mutex.java:1162) [catch] at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:171) at java.awt.EventQueue.dispatchEvent(EventQueue.java:454) at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:234) at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:184) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:178) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:170) at java.awt.EventDispatchThread.run(EventDispatchThread.java:100) > After that I get the folow exception:
Which is different exception. So at least some progress ;)
What "and have cleaned my userdir" does mean? Did uou delete just $USERDIR/var?
Be sure you delete (and backup if you need so) *whole* $USERDIR and start
netbeans (they will crate new one). Or use --userdir $ANOTHER_DIR.
Also included exception is not complete and none of the lines is from apisupport
module. Please *attach* (see "Create a new attachment" link, it is much more
readable than included stacktraces) again complete stacktrace.
BTW I occasionally get the AIOOBE from NbPresenter.superShow as well. I doubt it has much to do with apisupport; I have no idea what it means. Probably a core/windows bug. Ultimately a JDK bug that it doesn't report a better error (has an internal inconsistency in the Component impl); looking at sources, it seems that there are debug flags for this stuff (not assertions, why??) but they are disabled in JDK release builds. Created attachment 24052 [details]
message.log
It concerns the following: All folders were deleted in UserDir. After first starting of netbeans 4.2dev I start netbeans again and than I try to create a new project. Now I get an Exception dialog. The detailed Exception see in attachment messages.log. Reassigning for evaluation, but as I say it looks like an AWT bug. How can we handle this AWT bug? Pass it to the Mac JDK development I guess. Milos, any chance you know what this type of error is about? I remember we had such a report some time ago. I wasn't able to reproduce, but I figured there was such error in sun's jdk and was fixed. So filed an issue at apple's bug report system, with teh assumption it's the same issue as the sun jdk's. They closed the report because they could not reproduce and I didn't have a simple test case. #52187 is the original issue. does it happen both on 1.5 and 1.4? (i'm mostly running under 1.4.2 and I've done a lot of new projects and never encountered it) It 's happen on both JDK. 1.5 and 1.4.2 what exactly is your hardware? maybe we have a similar machine here. my hardware: Computername: Power Mac G5 Computermodell: PowerMac7,3 CPU-Typ: PowerPC G5 (2.2) Anzahl der CPUs: 2 CPU-Geschwindigkeit: 1.8 GHz L2-Cache (pro CPU): 512 KB Speicher: 1 GB Busgeschwindigkeit: 900 MHz Boot-ROM-Version: 5.1.8f7 I have almost identical setup: Machine Name: Power Mac G5 Machine Model: PowerMac7,2 CPU Type: PowerPC 970 (2.2) Number Of CPUs: 1 CPU Speed: 1.6 GHz L2 Cache (per CPU): 512 KB Memory: 1.25 GB Bus Speed: 800 MHz Boot ROM Version: 5.1.4f0 One difference that could be significant are the 2 processors that you have. I can try make test on another appel machine with one prozessor I tested netbeans now on one prozessor mashine: get no exception. But what is with my dual prozessor machine? The version 4.1 of netbeans works properly. What is with 4.2? I have downloaded the last version from 23.08.2005. At first start no exception, but at second start I get a new exceptions. What is wrong? messages.log folows. Created attachment 24180 [details]
messages.log of last version from 23.08.2005
#61954 is possibly a duplicate of this one. I tested the last version of netbeans 4.2 on G4. I get Exception again. Please fixed this bug or explain how to handle this bug. Otherwise we must to decide for another plattform. It's a pity, because the netbeans have so many features now. *** Issue 60732 has been marked as a duplicate of this issue. *** hrebejk, anything special that the project creation wizard is doing? like constructing the UI in non-AWT thread? *** Issue 61954 has been marked as a duplicate of this issue. *** Why is this in core/windows?? *** Issue 67555 has been marked as a duplicate of this issue. *** *** Issue 59998 has been marked as a duplicate of this issue. *** *** Issue 68889 has been marked as a duplicate of this issue. *** Too late for NB5.0, please reevaluate. *** Issue 71063 has been marked as a duplicate of this issue. *** I had similar problem after a fresh install of Netbeans 5.0 RC2 (no previous user dir). I had just started the IDE and classpath scanning was not finished. Clicked on toolbar icon to create a new project and when the window opened I saw the exception icon on the lower right flashing. My computer system info: Nome computer: iBook Modello computer: PowerBook4,3 Tipo CPU: PowerPC 750 (2.2) Numero CPU: 1 Velocità CPU: 800 MHz L2 Cache (per CPU): 512 KB Memoria: 384 MB Velocità bus: 100 MHz Versione Boot ROM: 4.5.2f2 Numero di serie: UV2460PAN5A Created attachment 28502 [details]
Log file for previous comment
I also see this with Creator 2 running on iMac Intel Duo. Since is a single processor with Dual Core. 2GHz CPU, 2 Gig Ram. This bug is not so good because it hits users who have just installed the product when they first try to create a new project and so it impacts our chance of retaining the user. I see the exception in the duplicate bug 23584, java.awt.Container.createHierarchyEvents(Container.java:934) *** Issue 52187 has been marked as a duplicate of this issue. *** Can reproduce it reliably with fresh userdir by clicking on New Project icon on 3.6GHz Intel based station, cannot reproduce on 1.4GHz PowerBook G4. *** Issue 73016 has been marked as a duplicate of this issue. *** *** Issue 73583 has been marked as a duplicate of this issue. *** Lot of duplicates. I think we have to investigate the reason, if this is an JDK issue, it has to be filed, if not it's up to us to solve the problem. *** Issue 73784 has been marked as a duplicate of this issue. *** *** Issue 75134 has been marked as a duplicate of this issue. *** *** Issue 75496 has been marked as a duplicate of this issue. *** *** Issue 76105 has been marked as a duplicate of this issue. *** *** Issue 76040 has been marked as a duplicate of this issue. *** *** Issue 75924 has been marked as a duplicate of this issue. *** *** Issue 76444 has been marked as a duplicate of this issue. *** *** Issue 76257 has been marked as a duplicate of this issue. *** *** Issue 76651 has been marked as a duplicate of this issue. *** Created attachment 30543 [details]
textual diff of the suggested change.
Created attachment 30544 [details]
6.0 trunk projectui jar with custom patch applied.
I think I figured what is the problem. The UI code was partly called from non-AWT thread. I have prepared a patch, however there is a problem because I cannot verify if it really fixed it or not, because it was working for me before the fix as well. Could anyone who manages to reproduce on his setup please try the patched version? steps to try out the patch. 1. download the latest daily build of 6.0 2. download the attached jar file. 3. overwrite the jar file in the original location. (on macosx you need to browse the Netbeans.app folder content and find where the file is located and overwrite it 4. run netbeans and verify it works now. *** Issue 76642 has been marked as a duplicate of this issue. *** Is this scheduled to be fixed in the 5.5 release (this has been around since 4.2 right)? The error happens "right out of the box" on Intel Macs. This is a VERY bad impression to give new users. I am haveing a hell of time getting people to consider using this tool when the first screen they see is an exception getting thrown...... Do we know if its a Netbeans issue or an Apple/Java AWT issue? Should I be opening a bug report at Apple? Pat pattyd19:
> Is this scheduled to be fixed in the 5.5 release ?
We need to know the fix, please could you try the patch attached here by mkleint
and try it again? It will really help us.Once we know the fix, it will be merged
to NB 5.5.
Thanks in advance.
*** Issue 76712 has been marked as a duplicate of this issue. *** comments from pattyd19: ----------------------- I pulled down the daily and ran it it without the patch. This problem does not exist in the "200605211800" build. Do you still want me to apply the patch to the daily build? I confirmed that the issue remains w/ the 5.5 version on my box. So to summarize: 5.0 no issue 5.5 throws AIOOBE Daily no issue ----------------------- Does it mean: it is working fine in Dev builds? Milos, has there been any possible patch already applied? Anyway I think we need the fix for NB 5.5 as well (fix for NB 5.0 hot-fixes AU should be welcome I think) ... my current evaluation of the problem is that the UI is constructed and shown from a non-AWT thread, which results in random problems. The bad code is in trunk and as well in 5.5. I was never able to reproduce on my macosx machine. Some people get it at random, some seem to have close to 100% hitrate. The fact that it works for one person on 6.0 and not at all on 5.5 seems to be actually a sign of the bug's randomness. I suppose that 5.5 has a different set of project templates or takes a different time to load. I will prepare another patched jar for 5.5. Created attachment 30575 [details]
the 5.5 dev version of the projectui module with the patch applied.
i've added the 5.5 version of the module affected. *** Issue 77132 has been marked as a duplicate of this issue. *** anyone tried? applied to trunk. marking as 5.5 candidate due to high number of duplicates and bad impact on first use of the IDE. I am using the patch in 5.5 for a while and I am not able to reproduce it now. *** Issue 77949 has been marked as a duplicate of this issue. *** *** Issue 78217 has been marked as a duplicate of this issue. *** For me the 5.5 patch also seems to work. Thanks! *** Issue 78912 has been marked as a duplicate of this issue. *** *** Issue 77866 has been marked as a duplicate of this issue. *** *** Issue 79881 has been marked as a duplicate of this issue. *** *** Issue 79975 has been marked as a duplicate of this issue. *** Created attachment 32115 [details]
Screen shot of issue
This issue still exist in release 2 of 5.5, did the patch not make it into this release? Created attachment 32116 [details]
Screen shot of issue w/ Release 2
*** Issue 80883 has been marked as a duplicate of this issue. *** issues are generally marked as fixed when they are fixed in trunk. this one is marked as 5.5_candidate meaning it ought to be fixed in 5.5 as well. once it's fixed in 5.5 the target milestone will change to 5.5 instead of the current Dev. *** Issue 80513 has been marked as a duplicate of this issue. *** *** Issue 81125 has been marked as a duplicate of this issue. *** integrated into release 5.5 branch *** Issue 81433 has been marked as a duplicate of this issue. *** This exception still exists on NB 5.5 Beta 2 using JDK 1.6 (b85). Since this is a very very highly visible bug, not sure why the fix is till not in NB 5.5 Beta 2. This issue is reproduced in NB 5.5 Beta2 on MacOSx petersl, pcmreddy: please read the previous comments. this was integrated into 5.5 *after* 5.5 beta2 *** Issue 82818 has been marked as a duplicate of this issue. *** *** Issue 83037 has been marked as a duplicate of this issue. *** *** Issue 84108 has been marked as a duplicate of this issue. *** *** Issue 74623 has been marked as a duplicate of this issue. *** *** Issue 84495 has been marked as a duplicate of this issue. *** *** Issue 85077 has been marked as a duplicate of this issue. *** *** Issue 85308 has been marked as a duplicate of this issue. *** *** Issue 85632 has been marked as a duplicate of this issue. *** *** Issue 87314 has been marked as a duplicate of this issue. *** *** Issue 87568 has been marked as a duplicate of this issue. *** *** Issue 74756 has been marked as a duplicate of this issue. *** |