Community
Participate
Working Groups
The RAD 8.0.2/RTC 3.0 combination is built on Eclipse 3.6.2. This crash is reproducible 100% of the time, as soon as a "Work Item editor" gets focus. The setup is onerous - I have the list of steps in email. If possible, this should be found and fixed (if it's an SWT problem) before 3.7 ships.
JAWS does not crash when IAccessible2 is not used, i.e. if Eclipse is launched with -vmargs -Dorg.eclipse.swt.accessibility.UseIA2=false
I have run out of time to investigate this before 3.7 ships. It needs to be investigated with the JAWS developers for 3.7.1. Changing target milestone. The furthest I got in my investigation was to see that SWT doesn't seem to be returning anything bad, like null pointers, to JAWS. All of the data returned seems normal. I need help from the JAWS folks to explain why they are crashing so that I can see if our code is somehow causing it.
What is the current status of this defect ? Any plans to fix this problem in the near future ?
Carolyn is on vacation. She will investigate it when she is back.
Thank you very much for the timely response. We will wait for a reply back from you guys after investigation since this is going to be pretty basic function which affects our Accessibility Verification test (AVT). Thanks for the work around to use the VM arguments, which allows us to make progress with our AVT in the mean while. I did want to mention that all the products that are built on top of Eclipse 3.6.2 have this issue and causes JAWS to crash: 1. Eclipse Text editor 2. Java editor 3. RTC work item editor etc.,
Retargeting since Carolyn as on vacation.
I was able to replicate this JAWS crash by running the RTC Eclipse client ontop of a 3.6.2 version of Eclipse. Thank-you Pavan for suggesting this. I worked with a developer at FreedomScientific, and he found the problem. It was a buffer overrun when JAWS asked the application for its version string. He fixed the problem, and he believes the plan is for a JAWS 13 hot fix in early to mid November. Note that the crash does not happen in Eclipse itself. Eclipse returns "3.6.2" for its version string. But RAD and RTC return longer version strings, and those were crashing JAWS. So we believe that this bug is fixed, but the fix is not available until the next JAWS 13 hot fix. I am going to mark this bug as "Resolved - Not Eclipse", and remove the target milestone. When the hot fix is available and I have tested it, I will add a note to this bug report indicating that the fix has been verified.
Thanks Carolyn!! I will wait for your verification note.
I just tested RTC with JAWS 13.0.527 which is available today, and JAWS did not crash. Please get the latest JAWS, and try this out. Make sure to remove -Dorg.eclipse.swt.accessibility.UseIA2=false from your eclipse.ini file, and do not include it in the -vmargs on the command line. Enjoy!
