This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 243287 - Netbeans 8.0 & all versions from 7.1 crash on Ubuntu 12.04 / armhf (Samsung Chromebook)
Summary: Netbeans 8.0 & all versions from 7.1 crash on Ubuntu 12.04 / armhf (Samsung C...
Status: RESOLVED INCOMPLETE
Alias: None
Product: platform
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 8.0
Hardware: Other Linux
: P3 normal (vote)
Assignee: Antonin Nebuzelsky
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-03-26 13:00 UTC by solasola
Modified: 2014-04-18 13:22 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description solasola 2014-03-26 13:00:45 UTC
I would like to use Netbeans on my Samsung Series 3 ARM Chromebook (XE303C). This runs Ubuntu 12.04 / armhf with Java 7 Embedded JDK installed (1.7.0_45). The machine has 2GB RAM.

SquirrelSQL and Freemind run fairly well on it, so the hw is strong enough for heavyweight Java apps.

Netbeans 7.3.1 however, fails at startup and leaves no error message. The splash-screen is displayed and the progress goes to about 80-90% when everything disappears.

The exact same happens with Netbeans 8.0.

I have also installed Java Embedded JDK 8 and configured NB to run on it but there seem to be no difference in the result.

Netbeans 7.0.1 (installed from the Ubuntu repos) seem to run acceptably (bit on the slow side but tolerable).

ARM laptops/pcs are becoming powerful enough for daily use so the newer versions of Netbeans should run on them.
Comment 1 Antonin Nebuzelsky 2014-04-18 13:22:48 UTC
Please attach the following log:
http://wiki.netbeans.org/FaqLogMessagesFile

Also try running NetBeans from console to see if any error is logged to the console.

If the problem is a crash, there should be hs_err* file stored somewhere on your disk. Please attach here.

Then reopen this bug.