Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 360623

Summary: Expanding java-docs will crash the Eclipse
Product: [Eclipse Project] Platform Reporter: Milad Khajavi <khajavi>
Component: SWTAssignee: Platform-SWT-Inbox <platform-swt-inbox>
Status: CLOSED DUPLICATE QA Contact:
Severity: major    
Priority: P3 CC: arunkumar.thondapu, daniel_megert, eclipse.felipe, grant_gayed
Version: 3.7.1   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard:
Attachments:
Description Flags
Eclipse crash when clicking on expand hyperlink on the javadocs none

Description Milad Khajavi CLA 2011-10-12 03:53:11 EDT
1- create new android project
2- Write new BaseAdapter, at the end, hit ctrl+space
3- click on 'expand link' on javadoc
4- Eclipse will clash

or

1- open javadoc browser
2- refresh javadoc of android project
3- In some situation the Eclipse will crash

Here is my Error log of Eclipse: http://pastebin.com/G4b3VWK4

-- Configuration Details --
Product: Eclipse 1.4.1.20110909-0613 (org.eclipse.epp.package.java.product)
Installed Features:
 org.eclipse.jdt 3.7.1.r371_v20110810-0800-7z8gFcoFMLfTabvKsR5Qm9rBGEBK
Comment 1 Dani Megert CLA 2011-10-12 04:03:49 EDT
Does it also crash when looking at JRE Javadoc (e.g. HashMap)?
Comment 2 Dani Megert CLA 2011-10-12 04:05:38 EDT
>3- click on 'expand link' on javadoc
Can you attach a screenshot of this?
Comment 3 Milad Khajavi CLA 2011-10-12 04:20:05 EDT
Created attachment 204999 [details]
Eclipse crash when clicking on expand hyperlink on the javadocs
Comment 4 Milad Khajavi CLA 2011-10-12 04:21:25 EDT
(In reply to comment #1)
> Does it also crash when looking at JRE Javadoc (e.g. HashMap)?

No, I have lot of crash when reading Android Javadocs not on JRE Javadocs.
Comment 5 Dani Megert CLA 2011-10-12 04:24:21 EDT
(In reply to comment #3)
> Created attachment 204999 [details]
> Eclipse crash when clicking on expand hyperlink on the javadocs

Interesting Javadoc. Can you try this:
1. open the Javadoc view, then select the Android element, then expand
2. select the Android element and then Shift+F2 (this should open the Javadoc
   in an external browser)
Comment 6 Milad Khajavi CLA 2011-10-12 04:33:10 EDT
(In reply to comment #5)
> (In reply to comment #3)
> > Created attachment 204999 [details] [details]
> > Eclipse crash when clicking on expand hyperlink on the javadocs
> 
> Interesting Javadoc. Can you try this:
> 1. open the Javadoc view, then select the Android element, then expand
> 2. select the Android element and then Shift+F2 (this should open the Javadoc
>    in an external browser)

But when I hit shift+F2 the Javadoc open in new eclipse windows (Eclipse Browser in new tab). The problem is that some time the crash occurs when I reading Javadoc Browser, sometimes when I right click and then refresh the page, the eclipse will crash.
How to set eclipse to open Javadoc in external browser like Google Chrome?
Comment 7 Dani Megert CLA 2011-10-12 08:02:59 EDT
> How to set eclipse to open Javadoc in external browser like Google Chrome?
General > Web Browser preference page
Comment 8 Milad Khajavi CLA 2011-10-12 12:18:58 EDT
(In reply to comment #7)
> > How to set eclipse to open Javadoc in external browser like Google Chrome?
> General > Web Browser preference page

Thanks a lot for your consideration, temporarily I use external browser, But what about this bug? Is this a real bug or other thing?

I have reported another bug?! 360332 after days no any one consider it, could you please check it?
Comment 9 Dani Megert CLA 2011-10-13 05:22:21 EDT
(In reply to comment #8)
> (In reply to comment #7)
> > > How to set eclipse to open Javadoc in external browser like Google Chrome?
> > General > Web Browser preference page
> 
> Thanks a lot for your consideration, temporarily I use external browser, But
> what about this bug? Is this a real bug or other thing?
It needs to be investigated. Could you attach the HTML that works outside but causes Eclipse to crash?

> I have reported another bug?! 360332 after days no any one consider it, could
> you please check it?
I moved the bug to the right component.
Comment 10 Grant Gayed CLA 2013-06-27 11:52:52 EDT
The dump shows the native libraries for both WebKitGTK and XULRunner loaded, indicating that one of your plugins (probably the Android one) is explicitly creating a SWT.MOZILLA-style Browser, while the default SWT.NONE-style Browsers are using WebKit.  The mixing of these renderers in a shared process has proven to be problematic in many cases due to version differences between their common dependent libraries, so org.eclipse.swt.browser.DefaultType was introduced in 4.3 to enable plug-ins to specify the native type for SWT.NONE-style Browsers in order to avoid these conflicts.  Plug-ins that create a Browser with a renderer-specific style like SWT.MOZILLA are now required to set this, and I'm quite sure that this would fix your case.

Marking report as a duplicate of the report that introduced this property.

*** This bug has been marked as a duplicate of bug 390853 ***