in its .ini file and the browser that I create code had SWT.MOZILLA passed in to its constructor list. With this configuration, everything comes up and I can launch the about:config page to prove that I am indeed running xulruuner. However, when I close the application it then crashes. While I was investigating that crash, I noticed that when I pmap'ed the process, I saw a:

/usr/lib64/libwebkit-1.0.so.2.17.8

in its shared library list. Further, when I uninstalled webkitgtk, my crash went away.

I have done a grep through my code and there is no where in that code where I ever instantiate a browser that is not SWT.MOZILLA.

Can anyone tell me what other things might cause the webkit libraries to load and if there is anyway to stop it?

Hi Mark, there should only be a couple of possibilities here, unless
you're seeing an SWT bug:

1. You say that you're setting
-Dorg.eclipse.browser.DefaultType=mozilla, but your property name is
missing its "swt" segment (should be "-Dorg.eclipse.swt.br..."). Was
this just a typo in your question or do you actually have the wrong
property name in your eclipse.ini?

2. If there's another loaded plug-in that creates a Browser with style
SWT.WEBKIT then it will load webkit. Eclipse platform only creates
SWT.NONE-style Browsers, so do you have any other plug-ins that could be
doing this?

Grant

On 7/10/2013 11:55 AM, Mark Fishman wrote:
> Hello, for some strange reason my SWT browser always loads the webkit
> shared object libraries on my RH 6 machines if they are installed.
>
> I did the following test:
>
> On a Redhat 6.3 machine with the following installed:
>
> 1. webkitgtk-1.2.6
> 2. xulrunner 10.0.5
>
> My SWT 3.8 application had a:
>
> -Dorg.eclipse.browser.DefaultType=mozilla
> -Dorg.eclipse.swt.browser.XULRunnerPath=/usr/lib64/xulrunner-2/
>
> in its .ini file and the browser that I create code had SWT.MOZILLA
> passed in to its constructor list. With this configuration, everything
> comes up and I can launch the about:config page to prove that I am
> indeed running xulruuner. However, when I close the application it
> then crashes. While I was investigating that crash, I noticed that when
> I pmap'ed the process, I saw a:
>
> /usr/lib64/libwebkit-1.0.so.2.17.8
>
> in its shared library list. Further, when I uninstalled webkitgtk, my
> crash went away.
>
> I have done a grep through my code and there is no where in that code
> where I ever instantiate a browser that is not SWT.MOZILLA.
> Can anyone tell me what other things might cause the webkit libraries to
> load and if there is anyway to stop it?
>
> Thanks.
>
> -- Mark

Thanks for replying. The missing swt in the DefaultType specification was a typo when I was writing up this topic for the forum rather than in my actual code.

As for another plugin forcing a SWT.WEBKIT, it is possible but I don't think so. I did a very simple test where I created an application which only had the plugins that get included when you click the include required plugins plus one simple plugin that I created. The one plugin had a single view with a browser widget in it. The browser widget had a SWT.NONE in its constructor and I specified the -Dorg.eclipse.swt.browser.DefaultType=mozilla -Dorg.eclipse.swt.browser.XULRunnerPath=/usr/lib64/xulrunner-2/

flags. When I did a pmap on the launched java process, I still saw /usr/lib64/libwebkit-1.0.so.2.17.8 having been loaded in. I also saw the same thing when I ran it passing SWT.MOZILLA to the browser.

It should be noted though that I did not get a crash when I closed my test application.