Home » Eclipse Projects » Eclipse 4 » XWT locked on initialization in 4.1 / Linux GTK
| XWT locked on initialization in 4.1 / Linux GTK [message #650768] |
Wed, 26 January 2011 08:20  |
Eclipse User |
|
|
|
Hi,
My pure E4 4.1 application hangs on startup when starting the org.eclipse.e4.xwt bundle : the start method of the activator class calls XWT.runOnUIThread(...), which enters an infinite loop waiting for the XWT initializers to be initialized (XWT.checkInitialization())
The problem seems to be that XWT.checkInitialization() is called on bundle activation, before having initialized XWT, thus locking the calling thread.
Looking at the code of the XWT.runOnUIThread(...), it seems that this behaviour is specific to the GTK & Cocoa platforms.
Any help would be appreciated on how to properly initialize XWT on GTK.
Sun
|
|
| |
| Re: XWT locked on initialization in 4.1 / Linux GTK [message #650998 is a reply to message #650867] |
Thu, 27 January 2011 07:23  |
| Eclipse User |
|
|
|
| Yves YANG wrote on Wed, 26 January 2011 18:09 | We have tested it in GTK with Linux, not on GTK & Cocoa platforms. Please
fill a bug with a testcase if it is possible.
|
Well I guess I wasn't clear, in this case the problem happens with GTK on Linux (SuSE SLED 11.0 to be precise), and the code looks like the same initialization logic is used for GTK and Cocoa, but I did not try on Cocoa.
That's why I'm not sure it is a bug or an incorrect use of the XWT API.
The test-case is relatively straightforward : it is a pure-E4 application, with a bundle providing an e4-fragment to the E4 application mode. The activator of this bundle references the XWT class (this bundle plugs XWT UIs into the application), causing the org.eclipse.e4.xwt bundle to be loaded by OSGi, triggering it's activator and finally blocking on the checkInitialization() method, causing the app to hang on startup.
For information, the same process works fine with the E4 July 2010 release.
I'm quite new to E4, so if you guess this should still work, I will fill a bug report.
Sun
|
|
|
| Re: XWT locked on initialization in 4.1 / Linux GTK [message #651374 is a reply to message #650998] |
Sat, 29 January 2011 20:10 |
| Eclipse User |
|
|
|
We have tested it in the integration with SpringSource including OSGi. You
can find them in CVS e4/org.eclipse.e4.xwt/examples.
Best regards
Yves YANG
"Sun" <sun.volland@free.fr> wrote in message
news:ihrnoq$h0l$1@news.eclipse.org...
> Yves YANG wrote on Wed, 26 January 2011 18:09
>> We have tested it in GTK with Linux, not on GTK & Cocoa platforms. Please
>> fill a bug with a testcase if it is possible.
>
>
> Well I guess I wasn't clear, in this case the problem happens with GTK on
> Linux (SuSE SLED 11.0 to be precise), and the code looks like the same
> initialization logic is used for GTK and Cocoa, but I did not try on
> Cocoa.
>
> That's why I'm not sure it is a bug or an incorrect use of the XWT API.
>
> The test-case is relatively straightforward : it is a pure-E4 application,
> with a bundle providing an e4-fragment to the E4 application mode. The
> activator of this bundle references the XWT class (this bundle plugs XWT
> UIs into the application), causing the org.eclipse.e4.xwt bundle to be
> loaded by OSGi, triggering it's activator and finally blocking on the
> checkInitialization() method, causing the app to hang on startup.
>
> For information, the same process works fine with the E4 July 2010
> release.
>
> I'm quite new to E4, so if you guess this should still work, I will fill a
> bug report.
>
> Sun
|
|
|
| Re: XWT locked on initialization in 4.1 / Linux GTK [message #665868 is a reply to message #650998] |
Sun, 17 April 2011 11:09 |
| Eclipse User |
|
|
|
Hi,
I have this problem on Cocoa.
What is the bug number for this?
rgds Christophe
On 27-01-11 13:23, Sun wrote:
> Yves YANG wrote on Wed, 26 January 2011 18:09
>> We have tested it in GTK with Linux, not on GTK & Cocoa platforms.
>> Please fill a bug with a testcase if it is possible.
>
>
> Well I guess I wasn't clear, in this case the problem happens with GTK
> on Linux (SuSE SLED 11.0 to be precise), and the code looks like the
> same initialization logic is used for GTK and Cocoa, but I did not try
> on Cocoa.
>
> That's why I'm not sure it is a bug or an incorrect use of the XWT API.
>
> The test-case is relatively straightforward : it is a pure-E4
> application, with a bundle providing an e4-fragment to the E4
> application mode. The activator of this bundle references the XWT class
> (this bundle plugs XWT UIs into the application), causing the
> org.eclipse.e4.xwt bundle to be loaded by OSGi, triggering it's
> activator and finally blocking on the checkInitialization() method,
> causing the app to hang on startup.
>
> For information, the same process works fine with the E4 July 2010 release.
>
> I'm quite new to E4, so if you guess this should still work, I will fill
> a bug report.
>
> Sun
|
|
|
Goto Forum:
Current Time: Fri Jul 04 21:54:16 EDT 2025
Powered by FUDForum. Page generated in 0.03356 seconds |
Home