Community
Participate
Working Groups
An user reported that WSAD 5.0 (AFAIK is powered by Eclipse 2.0.1) crashed when using the new project wizard with JAWS 4.5. According to that user, this is 100% reproducible even on Eclipse 2.1.
We're going to need a little more information. How does Eclipse "crash"? Java VM dump? Dialog saying that there is an error? Is there any information in the .log file in the workspace/.metadata directory? Is there anything special in the user's setup or is it just a straight Win32 install on a Win2K machine? What Locale are they running with? We have done a lot of testing with Jaws (both versions 4.0 and 4.5) and have not seen these problems.
Here is the reply from the originator: I am running Eclipse 2.1 with a vanila install on the Win 2k standard client for e-business on a ThinkPad T23. I have tried running Eclipse with JAWS 4.0.103, 4.5.138, and 4.51.119. I have not had any crashes with JAWS 4.0. But, I have had crashes with JAWS 4.5 and 4.51. Also, JAWS 4.5 and 4.51 are silent on the main menu bar, they do not read the focus whereas JAWS 4.0 reads the focus reliably. I have had dialogues pop-up with errors. Here is text from a couple of them: graphic 725 Error Creating Java Project An error occurred while creating the Java projectgraphic 673 Reason: Problems encountered while setting project description. OK Details >> graphic 725 Help Error Help cannot be displayed. The embedded application server could not run helpgraphic 673 web application. Check the log for details. OK And, in deed, the log has lots of detail. Here is my .log: I had first installed WSAD 5.0 and had the same experience. Then I unstalled WSAD and tried Eclipse to see if the behavior was the same. When it was, I was doing some reading and stumbled across a post on the java accessibility list from someone else having the same problem. He recommended trying JAWS 4.0 ... and it works. There were significant changes in JAWS java support between 4.0 and 4.5. Now, Freedom Scientific recommends JRE 1.4. If you can tell me how to run it on 1.4, I'd give it a try.
Created attachment 4616 [details] .log The .log file is attached
Looking at the stack trace it looks like you are using jdk1.3.0_02. Eclipse supports JDK 1.3.1 and higher - this crash may not be JAWs related at all if you are using an incompatible JDK. Please see if this occurs with 1.3.1 or later. We have tested using JAWS 4.0 and 4.5 using 1.3.1 vms with no problem. If you want to run with a 1.4 or higher vm just replace the one in your eclipse/jre directory or your classpath with a higher version one. For JAWS it is likely using a VM you have on your path if there is one. Be sure that any java.exe on your classpath is a late enough version. To check if this is the case open a command prompt and execute java -version. If there is a java on your classpath you will know the version then.
Here is the reference to the required VM for JAWS 4.5 - http://www.freedomscientific.com/fs_products/software_jaws45newfea.asp
Although Freedom Scientific specifies the use of Java SDK 1.4.0 and Java Access Bridge 1.0.2 with JAWS 4.5, these requirements are specifically for applications implemented using AWT/Swing. Since Eclipse is implemented using SWT, which uses native widgets, JAWS can be used with Eclipse on Java SDK 1.3.1 (or the corresponding JRE). I strongly suspect the failures above were caused either due to the use of 1.3.0, or due to having conflicting JREs on your system path. The error log shows that it was unable to find net.dll (which it should have been able to even if you were running 1.3.0). Since the loadlibrary call is in a static method in java.net.InetAddress, this caused it to fail the initialization of InetAddress, which caused the subsequent NoClassDefFoundErrors (UniversalUniqueIdentifier refers to InetAddress). Note that you can run eclipse with a specific VM using the -vm command line option. For example: eclipse -vm c:\jre1.3.1\bin\javaw.exe I recommend trying this with a 1.3.1 or 1.4.x VM. Please let us know whether this fixes the problem for you.
I have implemented all suggestions with no change in results. I removed all JRE's listed in control panel. I removed all system path entries that pointed to a java.exe or javaw.exe. Now, as far as JAWS is concerned, there is no java on my system. I do have two JDKs installed: jdk1.3.0_02 and j2sdk1.4.1_02. Neither JDK is accessible via the system path at a command prompt and neither JDK has the access bridge installed (although that shouldn't matter as already pointed out). I am now starting Eclipse 2.1.0 using a shortcut with the following target: D:\eclipse\eclipse.exe -vm C:\j2sdk1.4.1_02\jre\bin\javaw.exe -data D:\Projects\eclipse\MyWorkspace When I run with JAWS 4.0, all works well. When I run with JAWS 4.51, I get crashes like those in the .log (.log.2003.04.22) I will attach. This .log has two crashes when trying to open the help table of contents, one while trying to create a new java project, and one while trying to close Eclipse just after attempting to create the new project. It is also worth noting that when running with JAWS 4.51.119, I observe the following: 1. It takes longer to start Eclipse (maybe 10 sec or so) 2. If I press/release alt and navigate the main menubar (file, edit, ...), JAWS is silent. My JAWS install is completely ordinary. I used the "automatic" install option and only made minor config changes like speech rate and keyboard layout after install completed. Today I am adding a braille display to my system. Even though it is not necessary, I will completely reinstall JAWS 4.51 and check Eclipse before I have made any changes at all to JAWS. I will report if anything is different. It is also important to note I am not the only user with this issue. Others on the java accessibility mailing list have experienced it.
Created attachment 4682 [details] .log with 4 issues: 2 opening help, 1 creating project, 1 closing Eclipse
We are using version 4.50.138 but if you have heard of this from others I wouldn't be surprised if 4.5x is all we need. The 1.4.1_02 you are using - is this the Sun VM from February 2003? Also please give steps to crash - as we can't replicate here thus far there may be a subtle step we are not doing the same way.
Using 2.1 with the Sun 1.4.1_02 February 2003 VM I can get the UnsatisfiedLinkError to occur (I will attach the log) so I think we have replicated the issue here - thanks for the extra info Matt. This problem did not occur with the IBM 1.3.1 RC2 VM - I will check with the 1.4.0 vm as well.
Created attachment 4683 [details] Log using the 1.4.1.02 Sun VM creating a java project STEPS 1) Start with a fresh workspace 2) Create a Java Project 3) Error will occur trying to create a java nature.
Same problem occurs with IBM 1.4.0 VM and with the 1.3.0 RC2 IBM VM using 4.5 and a fresh workspace.
I can confirm this Eclipse 2.1 and Websphere Studio 5.0 crash with jaws 4.5 and jaws 4.51 using both winnt 4.0 SP6 and Windows 98 Se, with following Virtual machines: Sun JDK 1.3.1, Sun JDK 1.4.0, SUN JDK 1.4.1 Eclipse crashes showing a dialog box "Java VM terminated: error code: - 1" There is no error in workspace\.metadata\.log file. To reproduce consistently the problem I just launch Eclipse with one of the jdk in a workspace that is non empty; just shiftctrl+f7 to switch current view a fiew time, arrow up and down in package explorer or navigator and eclipse crashes. All works perfectly with jaws 4.02 and below with every jdk ii've tried. I've Java Access Bridge 1.02 installed on the Windows NT machine, BUT NOT on the Win98 machine.
If you get a crash from the VM you should also have a javacore file. If you do please append it to this problem report.
Java core file? whats the name of the file?
It would be javacoreXXX.txt where the XXX is some sort of timestamp. It would likely be in your eclipse root.
Created attachment 4723 [details] Java core dump - wsad 5.0 Jaws 4.51
No javacore when running eclipse 2.1 with the various Sun sdks; I have the attached javacore dump when running wsad 5.0 with jaws 4.51
Another crash when running eclipse 2.1 with jaws 4.51, no javacore but the following dialogs which may be useful (translated in english italian messages)
Created attachment 4724 [details] Eclipse 21 crash dialog messages - jaws 4.51
I'd like to report that in addition to the crashes already reported, there is also a significant slow down in my computer when running eclipse and jaws 4.5.1. This can be observed specially when exploring the preference page.
I did some experimentation myself and found that the perspective switching is the easiest way to replicate the slowness.
Also note that I am running XP and there appears to be greater performance issues in 2k than on XP (Matt King has played his JAWS over the phone for me on 2K). We will investigate any 2K differences here but the really bad case was in perspective switching (this was bad on all platforms).
Created Bug 38194 for the performance issue
I may have isolated the root cause: the presense or absense of the Java Access bridge. With the Java Access Bridge installed, I can execute the crash repro scenarios (new Java project, Help - Help Contents) without error. That is, Eclipse executes normally, albeits quite slow. When I remove the Java Access Bridge from the configuration, the repro scenarios do crash, and I obtain stack trace similar to the logs above. I should note that in either configuration, I continue to see the other defects noted in this log, that is, the performance problems and the loss of voice in the menus. My configuration is JAWS 4.5.138 (demo version), SUN JRE 1.4.0_01, Access Bridge 1.0.2 (I know there's a 1.0.3 out now, but i didn't fetch it yet), and Eclipse 2.1. Java Access Bridge is at http://java.sun.com/products/accessbridge/.
For me, it can crash without the access bridge installed. I am attaching a log of this crash occuring while using JAWS 4.51.119 and Sun JVM 1.4.1_02. I was saving a file in the java editor when it occurred. It might be the case that there are more ways of reproducing this crash when the bridge is present, but it can definitely happen without the bridge.
Created attachment 5024 [details] .log for crash without java access bridge while saving a .java file
Matt, perhaps i worded my entry poorly, but the discovery on my configuration is that there is no crash with Access Bridge installed. There is a crash when the Bridge is not installed.
Here are my results, thus far, of attempting different combinations of JAWS, JVMs, Eclipse, and the java access bridge. Summary: Eclipse crashes and errors depend on the eclipse version, JVM version and whether or not the access bridge is present in the JVM as well as the JAWS version. There are four variables involved: 1. The version of Eclipse: I am trying the 5/28 and 6/11 integration builds. 2. The version of JAWS: I am trying 4.0.103 and 4.51.119. 3. The JVM: I am trying IBM JRE 1.4.1, Sun JRE 1.4.1, and the IBM J9. 4. Whether or not the access bridge is installed in the VM. I am using only Access Bridge 1.03. To uninstall the bridge, I am closing Eclipse, removing all 3 bridge files (accessibility.properties and the 2 jars) from the VM tree, and restarting Eclipse. I have also, in some cases, removed the 3 bridge DLLs from the Windows path (in those cases, I have rebooted as well). There are too many combinations for me to test. Someone else will have to pick up the rest. I have some preliminary findings below. Here are the test cases I am using: 1. Open eclipse and test the menu bar and menus. 2. Load help contents in IE 5.5. Follow a few links and close. 3. From the resource navigator, Create a new java project. 4. From the Java package explorer, create a new package. 5. Create a new class. 6. Edit and save the class. 7. delete the package. 8. delete the project. 1. Eclipse 6/11 integration build This version of Eclipse is not useable with JAWS, any version, as JAWS cannot track the cursor in the editor. At first I thought that was dependent on other aspects of the installation, but I found that it is not. Nonetheless, I did find: With the IBM 1.4.1 VM: 1. All tests complete with JAWS 4.0, with or without the access bridge. 2. With JAWS 4.51 and no access bridge, the menubar does not read, project creation fails, and help will not load. 3. With JAWS 4.51 and the access bridge, menubar does not read, Eclipse cannot find the Help contents, and all other tests complete. 2. Eclipse 5/28 integration build With the IBM 1.4.1 JVM: 1. With JAWS 4.0, with or without the access bridge, all test complete. 2. With JAWS 4.51 and no access bridge, help contents will not load; page not found error. Menus do not read. All other test complete. 3. With JAWS 4.51 and the access bridge, the results are the same as without the access bridge. With the Sun 1.4.1 JVM: 1. With JAWS 4.0, all test complete.
I have just retested the M1 3.0 build with the following conditions JAWS 4.51.119 Windows XP Eclipse build 3.0 M1 using the sidecar June 27 version 1.4.1 Sun JRE installed on my path (I assume this is one that JAWS would use). As it is just a JRE I do not have the access bridge installed. Using this parameters all of the tests Matt describe passed without a crash (although there are some issues with focus on the entries in the help view). However I can confirm that the text is not read using this build and does work with the 2.1.1 release - I will log this is a seperate bug.
I have logged Bug 39600 as a seperate bug for the Java Editor issue. This bug only occurs on build M1 and later and not in WindowEyes so I think that this is a tool specific problem. The performance on WindowEyes is quite good for this cases.
any news on this bug?
Freedom Scientific released an upgrade for JAWS 5.0 today. This upgrade includes the code that gets rid of the sluggishness we were seeing in Eclipse with 4.51 and 5.0. Anyone, who is authorized for 5.0 can download the upgrade from: http://www.freedomscientific.com/fs_products/software_jaws5intro.asp I have also tested this new version with WSAD 5.1.1 and the sluggishness is solved there as well. I think this problem is now solved.
I agree that this problem is solved using the new JAWS 5.0 update (5.00.809). All issues discussed here - performance, menus not being read, text editor not being read, etc. are all fixed. I have not had any crashes (but of course, I am running the latest eclipse with a fairly recent VM). I encourage folks to try the newest version of JAWS with eclipse 2.x (or WSAD versions built on older eclipse versions). I am closing this bug report. If there are still JAWS issues, please open new bug reports.
