UPDATE FROM MABULA
I have had a very rough 2 months unfortunately health wise. I was struck 3x in a row with bacterial infections. The second infection occurred after a routine hospital checkup and I became very sick. I had to rest and take a lot of antibiotics. Once I was recovering and restarting work 1 month ago, I again became sick. The infection was not yet gone, so even more antibiotics and rest was needed. Needless to say, it took a lot of my energy and I needed a lot of rest.
Finally, the infection is really gone and my energy is coming back step-by-step now and I have started work again. I am terribly sorry to have kept you waiting for support. I will address all outstanding questions and e-mails step-by step and will be on the forum daily from today.
APP 2.0.0-beta47 will come soon as well, a lot of work was already completed before I became very ill, so the release is also nearly ready for you. Beta47 will be much faster actually. Many workflows will be more than 2x faster, mosaics can even be 10x faster than before because registration really received a major boost... all compared to beta46. Before I release it, I will make sure that everything is working properly and then I will release it.
I just installed the beta43 on my linux PC (opensuse 15.6). It seem to work, but didnt done further tests til now. When starting APP with gtk-launch the following warning occurs on startup:
[0.003s][warning][gc] ** WARNING! INCORRECT SYSTEM CONFIGURATION DETECTED! **
[0.003s][warning][gc] The system limit on number of memory mappings per process might be too low for the given
[0.003s][warning][gc] max Java heap size (115856M). Please adjust /proc/sys/vm/max_map_count to allow for at
[0.003s][warning][gc] least 208540 mappings (current limit is 65530). Continuing execution with the current
[0.003s][warning][gc] limit could lead to a premature OutOfMemoryError being thrown, due to failure to map memory.
I'm just curious what that means? I'm using a Ryzen 5900X with 128GB Memory.
Hi @juergenn,
Thank you very much for reporting this. Did beta43 run fine despite that warning?
Beta43 uses a different internal memory configuration, this warning is definitely related to that. I will do some testing on my linux systems. Maybe I need to further adjust the new configuration to remove that warning.
I do think that APP 2.0.0-beta43 will run fine despite the warning. Did it? Or did you get an Out Of Memory issue?
Mabula
i tried a set of 460 lights, two sessions, different focal length. Bayer drizzle 1.5, droplet 1.0. LNC 1st degree, 3 iterations.
At the start again the warning, but it worked fine, no problems.
I started it with gtk-launch, after closing APP I get the following message:
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb)
Hi @juergenn,
Please update to 2.0.0-beta44 and let me know if those warnings are gone. I think it should be fixed with the adjustments for beta44 😉
How much RAM memory is in your Linux system?
Mabula
Hi Mabula,
i have 128GB of RAM. I run same project with 460 lights again. The warning is still there and also an error report file (I started with gtk-launch again). i attach both files (I had to rename the .log-file to .txt).
But the program run without problems, despite error/warnings.
Regards
Jürgen
Hi @juergenn,
Today, I have released 2.0.0-beta45. Can you test this and let me know if all is okay? Are the warnings still there or not?
You can find beta45 in the downloads section.
Mabula
Hi Mabula,
I testet Beta45 with the same set of files: everything is working ok and no more warnings 🙂
