2.0 beta 29, windows 11 crashing to desktop no errors, on pressing integrate?

I had the same problem on two different computers. I solved it by updating the bundled JRE to the latest update of the same version (21.0.2 to 21.0.4).

Posted by: @alfogator

↑

I had the same problem on two different computers. I solved it by updating the bundled JRE to the latest update of the same version (21.0.2 to 21.0.4).

I don't think you can download the JRE directly as it's a retired version, but from this link:

https://www.oracle.com/java/technologies/javase/jdk21-archive-downloads.html

you can download the JDK which contains the JRE.

I'm not at the computer that has it right now but from memory:

- Get the ZIP version and extract it somewhere, it will contain a JRE folder.

- make a copy of the AstroPixelProcessor install folder, so you don't tamper with the original install

- replace the folders inside APP which contain the JRE with the equivalent from the downloaded zip.

- launch APP from the new folder, it should use the updated JRE.

if you have difficulties in following the procedure I can be more precise when I get back to my computer.

Let me know if this solves the problem for you.

I'm having the same issues - have spoken to Mabula and he will release a new version with functioning JRE in the bundle but haven't got any ETA from him.

I did try to update the JRE by following the above note but it didn't work for me. APP wouldn't start after the update. It will be really helpful if you can kindly give me the instructions step by step (including which version of JRE and x86 or x64 etc?

Kind regards,

Bikram

Hi Bikrmam,

You can download the latest GraalVM 21 at this link:

https://download.oracle.com/graalvm/21/latest/graalvm-jdk-21_windows-x64_bin.zip

The current version as of today is graalvm-jdk-21.0.5+9.1

Unzip the file, inside you will find the usual jdk folders: bin conf include jmods legal lib plus three files: LICENSE README

Open the APP installation folder which normally is:

C:\Program Files\AstroPixelProcessor

inside you will find a folder named jre, rename it to something like jre_backup

Create a new empty folder inside the APP installation folder and name it jre

Move everything from the downloaded jdk folder inside the new empty jre folder

Windows will ask you for admin permission while you do these operations, it's normal.

Now launch APP, it should run just fine.

If you ever want to revert to the original bundled JRE just delete the new jre folder and rename the jre_backup back to jre.

Hi Alfonso,

Thanks so much for sharing the information above. The APP ran fine after the JRE update.

However, the crash kept happening- it did progress a bit longer after the JRE update but eventually it crashed on both analyse and register. I then changed the compatibility of the Eze to Windows 8 and this time the register ran fine. But upon trying to integrate, it crashed again. I haven't checked if it produced any useful logs anywhere as yet.

Any ideas, what could I check next?

Kind regards, 

Bikram

Hi all @markm75 @alfogator @bikramghosh,

Thank you very much for reporting this issue and for pointing out that the issue is probably caused by an incompatibility in the particular development platfrom (Oracle GraalVM 21.0.2) that was used with 2.0.0-beta29.

The weird thing still is that the problem is not manifesting on all windows 11 installations. On my windows 11 system all is perfectly stable with 2.0.0-beta29 for instance.

Anyway, I have made a beta30-test version for windows now that uses the most up-to-date version of GraalVM being version 23.0.1. Can you all please download and test this version and let me know if this solves the windows 11 issues.

https://appreleaseserver.s3.eu-central-1.amazonaws.com/2.0.0-beta30-test/AstroPixelProcessor-2.0.0-beta30-test-Windows-64-bit.zip

Hi all, @markm75 @alfogator @bikramghosh

Can you please try the newly released 2.0.0-beta30 for windows? You can download it here:

Astro Pixel Processor Windows 64-bit
https://appreleaseserver.s3.eu-central-1.amazonaws.com/latest-release/AstroPixelProcessor-latest-release-Windows-64-bit.zip

I have done a lot of testing on 2 different windows 11 machines and all is working without issues on these systems and they have the latest windows 11 updates as well. So it is hard to understand why on some windows 11 computers APP is crashing at the moment. I think a reason could be that our development platform has a compatibility issue with windows 11.

So version 2.0.0-beta29 used Oracle GraalVM 21.0.2 and I see that you were able to figure out that 21.0.5 was working more stable, right? the 21.0.5 must have had some fixes for windows 11 then.

APP 2.0.0-beta30 uses the latest version of Oracle GraalVM, version 23.0.1 and has all the updates from 21.0.5 and later of course.

Please let me know if this helps.

Mabula

Hi, I tried the beta30 version and so far it seems to be working fine.

The one thing that caught my eye when I saw @markm75 report is that both his and my machine have fairly recent hardware, 14900k cpu and 4090 video card and 7950x cpu with 4090 video card in my case. That's what prompted me to try an updated jvm.

Just a guess, you might have more data available on the issue.

Posted by: @alfogator

↑

Hi, I tried the beta30 version and so far it seems to be working fine.

The one thing that caught my eye when I @markm75 is that both his and my machine have fairly recent hardware, 14900k cpu and 4090 video card and 7950x cpu with 4090 video card in my case. That's what prompted me to try an updated jvm.

Just a guess, you might have more data available on the issue.

Hi Alfonso @alfogator,

Thank you very much for the feedback. Yes, the development platform also needs updates for supporting the latest hardware now and then for sure, this I know from experience with developing APP in the last 7 years. Oracle Java and GraalVM will certainly keep updating since they are very vital to many big multinationals worldwide for their infrastructure.

Hi Mabula, 

I'm also running on a fairly new hardware - 14th Gen CPU i9 14900K and 4070Ti GPU.

I understand the frustration that it's working in some cases - however I suspect it is because of certain prerequisites being met on those systems, as I have explained in my email to you eaelier today. If you can tell me all the dependencies then I can test it out. One of them I think is Visual Studio Builder components required for Graal.  Now as explained, I did try with Graal 23 but I noticed the cache is loading OpenJFX 21. I'm not sure where it is coming from but I have a feeling that those aren't compatible. 

Anyhow, alternatively I suggest you run it on a brand new / vanilla installation of Windows 11 instance - to replicate the similar environmental configuration. 

Kind regards,

Bikram

Hi Bikram @bikramghosh,

The installer of Astro Pixel Processor provides all requirements needed to be able to run it on any Windows installation.

The Visual Studio Builder or any other component of Visual Studio is not needed at all for running Astro Pixel Processor. That component would be needed if you compile/build an application with GraalVM. So only the application builder needs that component, not the user.

"Now as explained, I did try with Graal 23 but I noticed the cache is loading OpenJFX 21. I'm not sure where it is coming from but I have a feeling that those aren't compatible."

How can you possible see that OpenJFX 21 is used when you load/run Astro Pixel Processor 2.0.0-beta30? I can't myself I think. What kind of cache are you looking at? How do you run/install Astro Pixel Processor?

We can only provide support if you use Astro Pixel Processor as installed by the installer that we provide. People that try to hack/change how APP runs, like changing the installed JRE or anything else can't be supported, since we will lose all control. We purposely provide an installer with the correct java version which contains all requirements to make it easy for the user.

If I install Astro Pixel Processor with the installer, I install it for all users, so the application will come in the folder c:/Program Files/AstroPixelProcessor right?

If I look into the libs folder in there I also clearly see the javafx 23 being there which we would expect. So it simply can't use JavaFX 21, allthough it would be fully compatible even.

JavaFX is also only used for the file chooser window, to have a native windows looking file/directory chooser. So we only use JavaFX for this, not for anything else.

"Anyhow, alternatively I suggest you run it on a brand new / vanilla installation of Windows 11 instance - to replicate the similar environmental configuration."

I did, my windows 11 laptop has no java installed, no Visual Studio as well. And all works fine.

Please double check the error report that you get with 2.0.0-beta30, if that error report shows that the error happens each time in the same file, then we can at least know in which file there is a bug somehow on your system. If it errors each time in a different file, then your system is likely unstable and the errors are caused by your system crashing due to hardware setup issues.

Mabula

Hi Mabula,

I have uploaded few screen recording to the upload site. I have demonstrated that after removing openjfx cache under C:\Users\Administrator\.openjfx\cache; it gets recreated as soon as I start Astro Pixel Processor from the start menu. It will show you that it is loading version 21. I have no clue how it is being used or initiated within APP - that will be upto you to comment. I'm laying down my observations. 

In terms of other version of GraalVM - as mentioned in the thread above and in my emails, those were for experimental purposes to see if that alleviates the problem or not. I can confirm under the latest test it is OOB installation for APP.

In terms of crash - 3 out of 4 execution failed on the same file. I also attempted without that file and it crashed then too. 

I have uploaded the screen recording of these crashes as well. The error log behavior was inconsistent - it was not produced every single time for some reason.

I have uploaded the error logs to the test site as well. The first 3 error logs were for Register step and the 4th one was for integrate step. 

What I'm sensing from this is that the at the launch of the software it is potentially using from libraries that are of other Java version, which could be artefacts\remnants from another software \ JAVA installation. That OpenJFX version caching is perhaps just showing us that nature of problem. I'm not saying that OpenJFX is the problem. 

IMO the software should build it's own cache with correct version of the libraries, if everything has been supplied with the installer. I have a feeling that's not what is happening. 

Hope this will give you additional details for the investigation. 

PS - I ran a subsequent test by forcing the cache to be renamed to 23.0.1+4 but it still created a cache for 21.0.2.+5

Kind Regards,

Bikram

Hi Bikram @bikramghosh,

Thank ou very much for all the details in your response.

I have tested this openJFX cache with 2.0.0-beta30. I removed all existing openJFX caches before starting APP. Once beta30 start, there is only cache for 23.0.1+4 on my systems. So if cache for oepnJFX 21 pops up on your system, I can only conclude that you are still starting beta29 ir the beta30-test version somehow? Did you remove APP completely before re-installing beta30?

From your videos, I actually see that you are not using 2.0.0-beta30 but the temporary 2.0.0-beta30-test version which does still use JFX 21.

Please download 2.0.0-beta30 here https://appreleaseserver.s3.eu-central-1.amazonaws.com/latest-release/AstroPixelProcessor-latest-release-Windows-64-bit.zip and you will see it uses JFX 23.

Now relating to your crashes, this openJFX version does not relate at all to your crashes. APP only uses OpenJFX for displaying the file/directory chooser. So if OpenJFX was the issue, the crash would happen when you try to load files or choose a directory.

"In terms of other version of GraalVM - as mentioned in the thread above and in my emails, those were for experimental purposes to see if that alleviates the problem or not. I can confirm under the latest test it is OOB installation for APP"

I am not sure what you mean by OOB? Out Of Bounds perhaps. Then your assumption is wrong I am afraid. GraalVM 23 can be used without issues with openJFX 21 and also vice versa, GraalVM 21 can be used without issue with openJFX 23.

GraalVM and OpenJFX are both separate development platforms where openJFX only tries to mimic the java JDK version numbering and release dates. Hope that clarifies it? The development platform creates it's own cache on your system, this is quite normal and something we want actually and I can not change that nor need to change that from a developers point of view.

From your videos I see that you use the TIFs, please use the DNGs, they have better data actually and will produce a better final result.

Now regarding the windows crash logs.

The crashes occur in the development platfrom files which are very well tested and used by anyone worldwide that uses Oracle Java or GraalVM.\

hs_err_pid21216.log

# Problematic frame:
# C [ucrtbase.dll+0x14f71]

hs_err_pid22796.log

# Problematic frame:
# J 8750 jvmci java.util.DualPivotQuicksort.sort(Ljava/util/DualPivotQuicksort$Sorter;

hs_err_pid14696.log

# Problematic frame:
# V [jvm.dll+0x4488a1]

hs_err_pid16980.log

# Problematic frame:
# J 8090 jvmci java.util.DualPivotQuicksort.sort(Ljava/util/DualPivotQuicksort$Sorter;

These files where the crashes occur are not created by the APP team, these files are from Oracle Java JDK. So if there are errors there, anyone that uses APP or Java will have the same crashes as you and they clearly don't. I never have these crashes on my 3 windows systems of which 1 is windows11 and the other 2 are windows10.

This leads directly into my initial conclusion, your system has a clear stability issue causing crashes at different places. If the crashes were caused by a software bug from our end, the crashes would happen consistently at the same moment with the same crash report and they would happen for all other APP users as well.

Random crashes at different moments are very well know to be caused by hardware instability. So double check your motherboard, the clocking of your CPU, if possible set it at a lower rate, check the cooling of your motherboard and CPU, finally do a 24 hour RAM test to make sure not one of your RAM modules is bad.

To be sure, I just ran your data with the TIFs and the same settings as shown in your videos and all works fine on my windows 11 system. In star analysis, I set the #stars target to 2500.

Hope this clarifies it? Please double check your hardware. APP is very tough on the computer's resources so yes, APP can crash or crash your operating system where other software will not.

Mabula

Hi Mabula,

Thanks for looking into this issue and providing the necessary fixes.

I have finally managed to resolve the issue - turns out there was some incompatibility with JAVA and the firmware for the motherboard on my computer. I checked all the settings you mentioned and ran RAM test for couple of times.

Everything looked alright but APP was still failing. Did further research and found out about the an updated firmware. 

APP ran file with - I ran the register and integrate successfully.

Thanks again.

Kind Regards,

Bikram

Dear Bikram @bikramghosh,

You are most welcome! Thank you very much for invetigating your computer's hardware and the firmware of your motherboard. I am very glad that the firmware update fixed the issue 😊 that is really great news!

Issues like this can be complicated and confusing, so I thank you very much for your patience with me as well.

Mabula