Bug 27225

Summary:	ImageJ crashes at startup
Product:	Mageia	Reporter:	Cyril Levet <cyril.levet0780>
Component:	RPM Packages	Assignee:	Java Stack Maintainers <java>
Status:	RESOLVED FIXED	QA Contact:
Severity:	critical
Priority:	Normal	CC:	geiger.david68210
Version:	Cauldron	Keywords:	Triaged
Target Milestone:	Mageia 8
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	imagej-1.52k-2.mga8.src.rpm	CVE:
Status comment:

Description Cyril Levet 2020-08-30 16:02:28 CEST

Description of problem:
ImageJ crashes at startup with a "Could not create the Java Virtual Machine error". ImageJ main windows is not displayed. The following message is displayed when launching imageJ:

Image display and analysis program. Opens formats including:
UNC, Analyze, Dicom, NIFTI, Tiff, Jpeg, Gif, PNG ...

imagej [options] image [ image2 ... image3 ]
    -h        print help and more options
    -o        open images in an open ImageJ panel
    -p <N>    open images in ImageJ panel number <N>
    -x <MB>   set available memory (default=768 max=4939)

Open other images in this ImageJ panel as follows:
  imagej -p 1 <image1> [<image2> ... <imageN>]

Unrecognized option: -d64
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.


Version-Release number of selected component (if applicable): imagej-1.52k-2 java-11-openjdk-11.0.9.2-0.0.ea.1.mga8


How reproducible: Always


Steps to Reproduce:
1. Launch "imagej" from a terminal

Comment 1 Aurelien Oudelet 2020-08-30 20:09:23 CEST

Hi,

Thanks reporting this. Currently, Java packages are in the long process to be rebuild.
Meanwhile, this could be pinpointed to our Java Stack maintainers.

(Packagers: Please set the status to 'assigned' if you are working on it)

Keywords: (none) => Triaged
Assignee: bugsquad => java
Target Milestone: --- => Mageia 8

Comment 2 David GEIGER 2020-09-02 08:08:57 CEST

Is this issue now fixed with new updated imagej?

CC: (none) => geiger.david68210

Comment 3 Cyril Levet 2020-09-03 23:28:30 CEST

No, new version 1.53d does not fix the problem. Error messages are the same.

Comment 4 David GEIGER 2020-09-04 09:11:44 CEST

So ok should be fixed with imagej-1.53d-2.mga8!

Comment 5 Cyril Levet 2020-09-04 22:29:07 CEST

It works with the last version. Bug is fixed. Thanks.

Resolution: (none) => FIXED
Status: NEW => RESOLVED