[JBoss JIRA] (JBIDE-16290) Bugs using SWT over GTK3
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16290?page=com.atlassian.jira.plugi... ]
Snjezana Peco commented on JBIDE-16290:
---------------------------------------
I have created a workaround (https://github.com/jbosstools/jbosstools-central/pull/199) that enables GTK3 for the central tests. I'm not sure why the previous code works with GTK2, but throws an exception when using GTK3.
I think there is a bug in GTK3 or SWT GTK3 that allows a control to be painted before it is completely created.
> Bugs using SWT over GTK3
> ------------------------
>
> Key: JBIDE-16290
> URL: https://issues.jboss.org/browse/JBIDE-16290
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform
> Reporter: Mickael Istria
> Assignee: Snjezana Peco
> Fix For: 4.2.x
>
>
> This ticket is meant to list the bugs related to GTK3 affecting JBDS:
> * JBIDE-16280 VPE/XulRunner crashes workbench
> * https://bugs.eclipse.org/bugs/show_bug.cgi?id=420581
> * Central tests uses SWT_GTK3=0 in its pom.
> We should make sure all SWT issues we met are reported upstream and that we provide the necessary assistance to SWT developers to make sure everything will be stable for Luna/GA.
> On Linux, most issues can be "hidden" by setting SWT_GTK3=0, but that's definitely not something we want to rely on for JBDS, as SWT over GTK2 will not be maintained in future.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBIDE-16290) Bugs using SWT over GTK3
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16290?page=com.atlassian.jira.plugi... ]
Snjezana Peco commented on JBIDE-16290:
---------------------------------------
{quote}
JBIDE-16280 VPE/XulRunner crashes workbench
{quote}
We are using our own version of XULRunner compiled with GTK2. An application (JBDS, Eclipse, etc) can't load different versions of a library (GTK2 and GTK3, for instance).
These are possible solutions:
- compiling XULRunner with GTK3 (the best solution in my opinion)
- removing/disabling XULRunner/VPE
- using GTK2
{quote}
> the tests run with GTK2 on Jenkins
Where is this configured in tests?
{quote}
https://github.com/snjeza/jbosstools-central/commit/6526bfe6017112f573b79...
{quote}
Can you please give details about what's exactly failing in Central tests that made you set SWT_GTK3=0
{quote}
I have already described the issue. See https://issues.jboss.org/browse/JBIDE-16282?focusedCommentId=12930558&pag...
Disabling GTK3 solves the issue. I will check if it is possible to solve it without disabling GTK3.
Anyway, the main issue is related to XULRunner. Porting it to GTK3 isn't trivial.
We could do the following:
- if a user starts Eclipse with GTK3, we would disable XULRunner (the VPE editor)
- if a user tries to open the VPE editor, we would warn him that the VPE editor requires GTK2 and would describe the way to run Eclipse with GTK2(export SWT_GTK3=0; ../eclipse)
> Bugs using SWT over GTK3
> ------------------------
>
> Key: JBIDE-16290
> URL: https://issues.jboss.org/browse/JBIDE-16290
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform
> Reporter: Mickael Istria
> Assignee: Snjezana Peco
> Fix For: 4.2.x
>
>
> This ticket is meant to list the bugs related to GTK3 affecting JBDS:
> * JBIDE-16280 VPE/XulRunner crashes workbench
> * https://bugs.eclipse.org/bugs/show_bug.cgi?id=420581
> * Central tests uses SWT_GTK3=0 in its pom.
> We should make sure all SWT issues we met are reported upstream and that we provide the necessary assistance to SWT developers to make sure everything will be stable for Luna/GA.
> On Linux, most issues can be "hidden" by setting SWT_GTK3=0, but that's definitely not something we want to rely on for JBDS, as SWT over GTK2 will not be maintained in future.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBIDE-16286) CDI builder (not import, workspace rebuild) is very slow in wildfly
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16286?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-16286:
-----------------------------------------------
[~adietish], what is value of -Xmx VM argument?
> CDI builder (not import, workspace rebuild) is very slow in wildfly
> -------------------------------------------------------------------
>
> Key: JBIDE-16286
> URL: https://issues.jboss.org/browse/JBIDE-16286
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.1.1.Final
> Reporter: Andre Dietisheim
> Assignee: Viacheslav Kabanovich
> Priority: Critical
> Fix For: 4.1.2.Final, 4.2.0.Alpha2
>
> Attachments: cdi-builder.ogv, thread-dump-7_05.txt, thread-dump-7_19.txt, VisualVM 1.3.2 _083.png
>
>
> When working in a wildfly workspace with all wildfly projects imported and CDI builder enabled, workspace rebuilds (that you trigger by changing poms and then do maven update project) are a lot slower than without it. Re-building the whole workspace can easily take up to 20 minutes for me.
> Hard to give more general purpose details, I did a quick screencast to give an impression how slow things are for me.
> [^cdi-builder.ogv]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBIDE-16280) VPE/XulRunner crashes workbench
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16280?page=com.atlassian.jira.plugi... ]
Denis Golovin edited comment on JBIDE-16280 at 12/12/13 12:19 PM:
------------------------------------------------------------------
You can comment it here in eclipse bugzilla as well https://bugs.eclipse.org/bugs/show_bug.cgi?id=423870
was (Author: dgolovin):
Yo can comment it here in eclipse bugzilla as well https://bugs.eclipse.org/bugs/show_bug.cgi?id=423870
> VPE/XulRunner crashes workbench
> -------------------------------
>
> Key: JBIDE-16280
> URL: https://issues.jboss.org/browse/JBIDE-16280
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: xulrunner
> Affects Versions: 4.2.0.Alpha1
> Reporter: Mickael Istria
> Priority: Critical
> Attachments: hs_err_pid20688.log
>
>
> After an install of JBDS 8.0.0.Alpha1 from installer (built locally with fixes from JBDS-2861), the application crashes a few seconds after startup.
> JVM creates me a thread dump, that you can find attached. Here is the header:
> {code}
> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> # SIGSEGV (0xb) at pc=0x00007fdea49f3255, pid=18578, tid=140596949411584
> #
> # JRE version: 7.0_25-b30
> # Java VM: OpenJDK 64-Bit Server VM (23.7-b01 mixed mode linux-amd64 compressed oops)
> # Problematic frame:
> # C [libxul.so+0xc81255] JSD_DebuggerOnForUser+0x978a2
> #
> {code}
> I'm running on Ubuntu 12.04.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBIDE-16280) VPE/XulRunner crashes workbench
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16280?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-16280:
---------------------------------------
Yo can comment it here in eclipse bugzilla as well https://bugs.eclipse.org/bugs/show_bug.cgi?id=423870
> VPE/XulRunner crashes workbench
> -------------------------------
>
> Key: JBIDE-16280
> URL: https://issues.jboss.org/browse/JBIDE-16280
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: xulrunner
> Affects Versions: 4.2.0.Alpha1
> Reporter: Mickael Istria
> Priority: Critical
> Attachments: hs_err_pid20688.log
>
>
> After an install of JBDS 8.0.0.Alpha1 from installer (built locally with fixes from JBDS-2861), the application crashes a few seconds after startup.
> JVM creates me a thread dump, that you can find attached. Here is the header:
> {code}
> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> # SIGSEGV (0xb) at pc=0x00007fdea49f3255, pid=18578, tid=140596949411584
> #
> # JRE version: 7.0_25-b30
> # Java VM: OpenJDK 64-Bit Server VM (23.7-b01 mixed mode linux-amd64 compressed oops)
> # Problematic frame:
> # C [libxul.so+0xc81255] JSD_DebuggerOnForUser+0x978a2
> #
> {code}
> I'm running on Ubuntu 12.04.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBIDE-16280) VPE/XulRunner crashes workbench
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16280?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-16280:
-----------------------------------
Priority: Critical (was: Major)
> VPE/XulRunner crashes workbench
> -------------------------------
>
> Key: JBIDE-16280
> URL: https://issues.jboss.org/browse/JBIDE-16280
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: xulrunner
> Affects Versions: 4.2.0.Alpha1
> Reporter: Mickael Istria
> Priority: Critical
> Attachments: hs_err_pid20688.log
>
>
> After an install of JBDS 8.0.0.Alpha1 from installer (built locally with fixes from JBDS-2861), the application crashes a few seconds after startup.
> JVM creates me a thread dump, that you can find attached. Here is the header:
> {code}
> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> # SIGSEGV (0xb) at pc=0x00007fdea49f3255, pid=18578, tid=140596949411584
> #
> # JRE version: 7.0_25-b30
> # Java VM: OpenJDK 64-Bit Server VM (23.7-b01 mixed mode linux-amd64 compressed oops)
> # Problematic frame:
> # C [libxul.so+0xc81255] JSD_DebuggerOnForUser+0x978a2
> #
> {code}
> I'm running on Ubuntu 12.04.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBIDE-16280) VPE/XulRunner crashes workbench
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16280?page=com.atlassian.jira.plugi... ]
Vlado Pakan commented on JBIDE-16280:
-------------------------------------
I have it on Fedora 18 KDE
> VPE/XulRunner crashes workbench
> -------------------------------
>
> Key: JBIDE-16280
> URL: https://issues.jboss.org/browse/JBIDE-16280
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: xulrunner
> Affects Versions: 4.2.0.Alpha1
> Reporter: Mickael Istria
> Attachments: hs_err_pid20688.log
>
>
> After an install of JBDS 8.0.0.Alpha1 from installer (built locally with fixes from JBDS-2861), the application crashes a few seconds after startup.
> JVM creates me a thread dump, that you can find attached. Here is the header:
> {code}
> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> # SIGSEGV (0xb) at pc=0x00007fdea49f3255, pid=18578, tid=140596949411584
> #
> # JRE version: 7.0_25-b30
> # Java VM: OpenJDK 64-Bit Server VM (23.7-b01 mixed mode linux-amd64 compressed oops)
> # Problematic frame:
> # C [libxul.so+0xc81255] JSD_DebuggerOnForUser+0x978a2
> #
> {code}
> I'm running on Ubuntu 12.04.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBDS-2866) CordovaSim Debugger
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBDS-2866?page=com.atlassian.jira.plugin.... ]
Konstantin Marmalyukov commented on JBDS-2866:
----------------------------------------------
looks like impossible. Firebug lite is a script which opens a window you see. Firebug lite does not support debug protocol, it's a simple js which parse your webpage. The only think we can do here is "reopening" firebug window after any refresh, but it wouldn't help. Weinre cannot do it also. Weinre benefit to you - it is not closing, it reloads after refresh or url changing. But it takes some time, so when device is ready weinre does not connected.
> CordovaSim Debugger
> -------------------
>
> Key: JBDS-2866
> URL: https://issues.jboss.org/browse/JBDS-2866
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: browsersim, requirements
> Reporter: Burr Sutter
> Assignee: Ilya Buziuk
>
> The current FireBug Lite in CordovaSim has the following limitations:
> 1) When using LiveReload, the window closes with every reload
> 2) Various "page load" events with console.log statements are not visible in FireBug Lite console, like having console.log() in your deviceready
> http://screencast.com/t/RRGhV9PV
> Note: I forgot to add the Console Cordova plugin, not sure if that is necessary but the window closes, so not sure how I would see the message
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months