Bug 169919 - [Browser] Eclipse crashes when "Show in Browser" is requested
Summary: [Browser] Eclipse crashes when "Show in Browser" is requested
Status: RESOLVED WORKSFORME
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.1.2   Edit
Hardware: Other AIX Motif
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Grant Gayed CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2007-01-08 21:43 EST by Eleonora Ludin CLA
Modified: 2008-04-10 16:36 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Eleonora Ludin CLA 2007-01-08 21:43:22 EST
QAIX115 client - installed latest ClearCase Baltic spin with Eclipse 3.1.2.  
Go to Help ->Manage Configuration
Expand to CCRC - select License
License is displayed 
Click on button "Show In Browser'
JVM Terminated error appears - Eclipse crashed. Exit code=721035

I have preference web browser set to default.  I did not see this happen when I had mozilla selected as the browser
Comment 1 Branko Tripkovic CLA 2007-01-23 15:12:13 EST
this looks like a problem with SWT Browser component. But I think they do not support all browsers. What is your default browser?
Comment 2 Eleonora Ludin CLA 2007-01-24 10:38:59 EST
I don't know what the default browser was on the machine where this defect was found. I suppose this could be a configuration error, however, Eclipse should handle it more gracefully if it either cannot find the browser or if the browser is not supported. 
Comment 3 Eleonora Ludin CLA 2007-01-24 10:44:31 EST
Also, why is the "Default Browser" option on the Preferences page available on AIX? It does not seem to be available on other Unix platforms.
Comment 4 Grant Gayed CLA 2007-02-28 15:16:37 EST
Sorry for the late response on this.

Are you able to attach the dump that you get when eclipse crashes?  The Browser widget is not supported on AIX, so invoking its constructor should just throw an error which the client is expected to catch and handle.  My initial thought was that the app you're using is failing to do this, but this should not cause a JVM crash.
Comment 5 Grant Gayed CLA 2008-04-10 16:36:27 EDT
Timed out, closing.  If this is still a problem with a recent eclipse release (3.4M6 is the latest milestone) and there is more info to provide then please reopen this report.