Community
Participate
Working Groups
Build Identifier: Eclipse SDK 3.6.1 We have a pdf link in our help. The first time the toc item is selected, the pdf book is opened properly. The second time the same toc item is selected, Eclipse crashes. There is no error message in the .log. Reproducible: Always Steps to Reproduce: 1. Start Eclipse SDK 3.6.1 and create a plugin using sample help template 2. Use the attached tocreference.xml to replace the generated one. 3. Save the attached PDF file in the plugin project 4. Launch runtime work bench and open the help 5. Click the toc item My topic under Main Topic 2 of Reference to open the PDF book 6. Click My topic again and the eclipse will crash
Created attachment 186635 [details] Toc file
Created attachment 186636 [details] PDF file
I have been able to reproduce the crash on Windows XP. I will investigate.
The problem also shows up in Eclipse 3.6 and Eclipse 3.5, it only happens when the href to the PDF document contains an anchor as in <topic href="dz9zr006.pdf#G29.1169203" >. The problem does not reproduce if an external browser is used. I'm surprised this has not been reported before since it exists at least back to Eclipse 3.5. The help system browser on Windows uses Internet Explorer to open the pdf file, I don't yet know if the problem is specific to one version of IE. I have IE 8 on my system, which version were you using?
My IE is 7.0.5730.13. But I was not using to open the help page. The preferences setting for Open help contents is "In the help browser".
When you open using the help browser on Windows you are indirectly using Internet Explorer - the SWT Browser widget is built on top of the native browser services, on Windows it uses Internet Explorer.
I noticed there was a patch appended to bug 334161. Is that patch supposed for this bug? Wonder how to try it out. Failed to find the ScopeSelectPart in the plug-in org.eclipse.help.ui.
I tried the patch attached to bug 334161 and it does fix this problem!
I verified using M20110119-0834 that this is now fixed by the patch in Bug 334161 *** This bug has been marked as a duplicate of bug 334161 ***