LPCXpresso IDE crashes on Ubuntu16.04:i386 installation

[thanassispapath]

Hello, I have just installed and activated LPCXpresso on Ubuntu16.04:i386 virtualbox vm. Whenever I try to import either a project or CMSISCore library (in order to create a project from scratch), the IDE stays with 100% cpu usage forever in Import dialog. Is this issue already known? Can I setup a project without the use of "Import Dialog"?

Thank you in advance

[lpcxpresso_supp]

We make make considerable use of VMs within our development team and are not aware of any problems in this area (or any other for that matter).

However we do not have the bandwidth to investigate issues seen when using VMs - if you can replicate on real hardware we will investigate further.

You can create projects using the comprehensive Wizards - simply click 'New Project' from the Quick Start panel.

Yours

LPCXpresso Support

[thanassispapath]

Thank you for reply,

I followed your suggestion and installed the LPCXpresso on real hardware

(I7-6700K,32GB RAM, OS Ubuntu16.04:amd64). I followed the instructions

in INSTALL.txt and installed also the required i386 libraries. The

problem still remains the same. The application hangs when invoking

Import Dialog and try import a project or library. Even cancelling the

operation is not possible, I explicit have to kill the process.

[lpcxpresso_supp]

Thank you for your report.

We have attempted to duplicate this problem, but on our Linux machines we see no issue. Fundamentally the import process is a file unzip and copy.

Can you confirm:

- when in the import process the hang occurs, for example, do you get the option to browse, do you see the project files etc.

- does this happen with any import, for example, can you import the supplied examples?

- is it the LPCXpresso process that is using 100% CPU?

- are you able to use the New project wizard to create projects in your workspace?

- if so can you debug these projects?

- have you successfully used LPCXpresso on a different version of Linux?

- are you able to confirm that a standard eclipse install can perform an import?

- have you used the default workspace?

- to attempt to duplicate this, can you provide us a link to the exact linux distribution you installed?

- finally, please confirm which version of LPCXpresso IDE you have installed.

Yours,

LPCXpresso Support

[thanassispapath]

The issue is fixed.

I found the main hint in eclipse log:

[Browser style SWT.MOZILLA and Java system property

org.eclipse.swt.browser.DefaultType=mozilla are not supported with GTK 3

as XULRunner is not ported for GTK 3 yet]

This message leads me finally to following url:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=423870

Summary: Eclipse crashes in libxul when

-Dorg.eclipse.swt.browser.DefaultType=mozilla

Solution is to disable GTK3 when starting LPCXpresso:

#!/bin/bash

export SWT_GTK3=0
/usr/local/lpcxpresso_8.1.4_606/lpcxpresso/lpcxpresso

[budinero]

Same problem here with  IDE v8.2.0, tested on arch and debian 64 bits. The ide hangs and eats 100% of one core after the import or after any project creation wizard. The workaround solves the issue...

[larrymyerscough]

Thanks Thanassis. I had exactly the same problem on my ubuntu (16.04?) system; and your workaround works for me too!

[graygirling]

> Solution is to disable GTK3 when starting LPCXpresso:

I would like to replicate your problem. So starting with a 64-bit 16.04 machine without GTK3 I added (64-bit) GTK3 (libgdk3.0-cil), but didn't find much difference (it continued to work).

LPCXpresso IDE is a 32-bit program (hence the requirement for 32-bit libraries).  Do you have an i386 version of GTK3 libraries or a 64-bit version?  Assuming it is 64-bit it shouldn't be being used by the IDE directly, so it's odd that it's making a difference. 

Was GTK3 part of another install?

Sincerely

LPCXpresso IDE Support

[thanassispapath]

Hello,

it fails on both amd64 and i386 installations. I suppose GTK3 is

installed with default ubuntu 16.04 desktop release.

[thanassispapath]

Thank you for your support.

Please find remarks inline: