Community
Participate
Working Groups
Build Identifier: M20100909-0800 Eclipse crashes almost immediately when attempting to access the web browser entry under the preferences/general. It gives no error messages, does not generate an error log. Reproducible: Always Steps to Reproduce: 1.click on window 2.click on preferences 3.Click on general 4.Click on web browser it crashes
(In reply to comment #0) > Build Identifier: M20100909-0800 > > Eclipse crashes almost immediately when attempting to access the web browser > entry under the preferences/general. It gives no error messages, does not > generate an error log. > > Reproducible: Always > > Steps to Reproduce: > 1.click on window > 2.click on preferences > 3.Click on general > 4.Click on web browser > it crashes Please provide exact version of your Linux and your desktop manager. Which browser are you using?
Created attachment 186005 [details] Helios config file
Mandriva Linux 2.6.33.7-desktop-2mnb #1 SMP Mon Sep 20 18:19:20 UTC 2010 x86_64 x86_64 x86_64 GNU/Linux running on a quad-core intel system. Desktop KDE
I use Firefox 3.6.13, but had not set any external browser up for the system. Presumably, it would be still set to use the internal browser. BTW my Galileo version of Essentris shows normal behaviour.
Could you attach a stack trace from the log file?
Where do I find it/how do I generate it. There is no errorlog generated under workspace/.metadata.
>There is no errorlog generated under workspace/.metadata. The file is '.log'. Also look for a javacore file (either in your home, the eclipse install or the JRE directory).
For US eclipse 3.6.1 has begun fail to on RHEL4 x86_64 platform. Eclipse 3.6.0 work normally. Additinal information can be founded here https://issues.jboss.org/browse/JBIDE-8040 https://issues.jboss.org/browse/JBIDE-8037
Copying Grant Gayed to see if he knows of any SWT changes between 3.6 and 3.6.1 that affect the browser on Linux. I just took a look at the second of the two logs Max submitted and saw these lines. org.eclipse.swt.SWTError: XPCOM error -2147467262 at org.eclipse.swt.browser.Mozilla.error(Mozilla.java:2414) at org.eclipse.swt.browser.Mozilla.unhookDOMListeners(Mozilla.java:2844) It's certainly possible that the problems reported by Max Areshkau have the same underlying cause as the original description although without a stack trace it's not possible to tell. Max, are you also using M20100909-0800 ( 3.6.1 )? I don't see any bugs fixed in the User Assistance component that are related to this area.
still no luck finding a java crash, but I did manage to restore the error log, by creating a new workspace. Here are the contents after a crash. !SESSION 2011-01-05 20:53:01.369 ----------------------------------------------- eclipse.buildId=M20100909-0800 java.version=1.6.0_22 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US Command-line arguments: -os linux -ws gtk -arch x86_64 !ENTRY org.eclipse.mylyn.tasks.ui 2 0 2011-01-05 20:53:20.699 !MESSAGE No search provider was registed. Tasks search is not available.
The above error log entry may be a red herring, when I tried to duplicate it. Essentris crashed, but no new log entry. Where to I look for a stack trace, crash dump. There doesn't seem to be anything useful in the workspace/.metadata/.log.
Yes, we are using eclipse 3.6.1 too.
Although the symptoms are different, I wonder if this is another case of bug 319123. Can you see if a recent 3.6.2 build like http://download.eclipse.org/eclipse/downloads/drops/M20110105-0951/download.php?dropFile=eclipse-SDK-M20110105-0951-linux-gtk-x86_64.tar.gz works better for you? And if not, can you see what is output by running the swt snippet at http://www.eclipse.org/swt/faq.php#printmozillapath ?
(In reply to comment #12) > Yes, we are using eclipse 3.6.1 too. The following JBoss Tools issues related to XPCOM errors and eclipse crashes are: https://issues.jboss.org/browse/JBIDE-8037 RHEL5 x86_64 https://issues.jboss.org/browse/JBIDE-8040 RHEL4 x86_64 Both are no longer crashing after moving to use Eclipse 3.6.2 M20110105-0951.
Glad to hear! Original reporter does http://download.eclipse.org/eclipse/downloads/drops/M20110105-0951/download.php?dropFile=eclipse-SDK-M20110105-0951-linux-gtk-x86_64.tar.gz fix your case as well?
It still gives the same behaviour with the 3.6.2. I ran the Helios 3.6.1 on a 32 bit Mandriva lap top. It works fine. I have been looking for log/crash files. There is noting in Workbench/.metadata/.log. What would the name be if JRE crashed and where would I find it?
I don't know if this is relevant, but when I try to view the error log from about..>installation details>view error log. It also crashes tracelessly even if there is an error log present.
Created attachment 186880 [details] error log file after loading plugins
Created attachment 186881 [details] Helios config file
The entries in the error log file does not correspond to the crashes. These occured while loading the CDT, linux tools, XML and PhP development kits.
It's easy to lose site of the original problem as the comments roll in. To summarize: - comment 1 and comment 17 indicate a problem accessing an external browser, so this would not be related to comments 13-15, and would not involve the Browser control - the problem was introduced between 3.5.x and 3.6.1 (comment 4), not between 3.6.0 and 3.6.1, since comment 8 is a different problem. Perhaps something bad is happening in swt's Program component. Can you try running the snippet below (just set its FULL_PATH_OF_AN_HTML_FILE)? Also, can you see if your hang happens with another session manager like Gnome? import org.eclipse.swt.program.Program; import org.eclipse.swt.widgets.Display; public class Main { public static void main(String[] args) { final String FULL_PATH_OF_AN_HTML_FILE = "..."; // fill this in Display display = new Display(); Program program = Program.findProgram(".html"); System.out.println("found program: " + program.getName()); System.out.println("execute result: " + program.execute(FULL_PATH_OF_AN_HTML_FILE)); System.out.println("launch result: " + Program.launch(FULL_PATH_OF_AN_HTML_FILE)); display.dispose(); }
It works fine under Gnome, I did not try other desktop managers. Attempting to run the snippet in scrapbook gives the following: Syntax error on token "import", assert expected. Possibly I am doing something wrong here I program C and C++ and am not very good at java.
If it works better under Gnome then this sounds like a problem in swt's Program support, so moving report there.
I have been unable to get any SWT snippets to run in the scrapbook. They fail with the same message. It would appear to me there is an issue with the SWT under 64 bit KDE desktop. I don't know if this is the same problem. Curiously, Subclipse also fails tracelessly and when I tried to run a snippet there to debug it gave me the same error message: 'Syntax error on token "import", assert expected'.
After some experimentation, I was able to figure out how to run the snippit. It runs, but produces no output. Snippet 128 from the SWT web site runs normally and opens the web page. I have noticed several other conditions which cause Eclipse to crash tracelessly, eg trying to open the error log, trying to open a auto-tool project and trying to expand the a Subclipse repository tree. In all the cases Eclipse crashes tracelessly. This only occurs with the 64bit version, running on KDE 4.3. When I run Gnome it works ok.
I am with exactly same problem here. I try click in Web Browser preferences and Eclipse close/quit. Arch Linux Eclipse SDK Version: 3.6.2 Build id: M20110210-1200
I am using KDE 4.
I found the problem. The problem happens using Firefox 4 and Eclipse. Eclipse isn't compatible with xulrunner 2.0 (used by Firefox 4). To solve the problem: Edit /usr/share/eclipse/eclipse.ini and put 1 or 2 lines: -Dorg.eclipse.swt.browser.XULRunnerPath==/usr/lib/xulrunner-2.0/ -Dorg.eclipse.swt.browser.UseWebKitGTK=true :) Bug references: https://bugs.archlinux.org/task/23392 http://changelogs.ubuntu.com/changelogs/pool/universe/e/eclipse/eclipse_3.5.2-8ubuntu3/changelog cya!
(In reply to comment #28) > -Dorg.eclipse.swt.browser.XULRunnerPath==/usr/lib/xulrunner-2.0/ > -Dorg.eclipse.swt.browser.UseWebKitGTK=true The second line is the one that's helping, don't add the first one.
Is this something that can be fixed for Eclipse 3.7? If it affects any users of Firefox 4.0 on Linux then a lot of people will run into it.
Comments 24-29 are actually a different problem, they are concerned with the Browser control, while this report is about specifying an external browser (SWT's Program class). Use of FF4 should not affect the latter.
Adding the : > -Dorg.eclipse.swt.browser.UseWebKitGTK=true or both does not fix the original problem. I think all of these issue must be related. I have heard that there are known problem with 64 bit swt, but I don't know the details.
Assigning, BG see comment 21 as a starting point.
(In reply to comment #29) > (In reply to comment #28) > > -Dorg.eclipse.swt.browser.XULRunnerPath==/usr/lib/xulrunner-2.0/ > > -Dorg.eclipse.swt.browser.UseWebKitGTK=true > > The second line is the one that's helping, don't add the first one. This worked. In fixing the GWT Designer css issue in eclipse
Webkit1 crashes have been resolved via Gtk3 & Webkit2.
