+1 vote
609 views

I recently updated to OpenLCA version 2.1, and it's started crashing when running calculations. I've tried running calculations both within the software, and externally to the software using the OLCA API, and in both cases it causes the software to crash. I currently have 10GB of memory allocated to OpenLCA on my machine, and have downloaded the libraries to speed up calculations as suggested in answers to previous, similar questions regarding the software crashing during calculations with version 2.0. When the software crashes, a text document is created, which reads: 

# A fatal error has been detected by the Java Runtime Environment:

#

#  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007fffe3542af1, pid=7624, tid=18284

#

# JRE version: OpenJDK Runtime Environment Temurin-17.0.5+8 (17.0.5+8) (build 17.0.5+8)

# Java VM: OpenJDK 64-Bit Server VM Temurin-17.0.5+8 (17.0.5+8, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, windows-amd64)

# Problematic frame:

# C  0x00007fffe3542af1

#

# No core dump will be written. Minidumps are not enabled by default on client versions of Windows

#

# If you would like to submit a bug report, please visit:

#   https://github.com/adoptium/adoptium-support/issues

# The crash happened outside the Java Virtual Machine in native code.

# See problematic frame for where to report the bug.

#

I wondered if this was an issue related to the code running through the API, as that was how the calculations were initiated the first time a crash occurred, but manual initiation in the software also resulted in crashes. 
in openLCA by (220 points)
by (220 points)
(Not sure if I should have a separate thread. Not sure how helpful the following is).
I second this. I had not experienced this with earlier versions. (Caveat: I didn't get this far with other versions).

I downloaded v2.1 on Jan 26th 2024. With 2.1 (I didn't play around with 2.0), the software crashes. It simply crashes and generates "hs_err_pid#####" txt files. The only difference to above is problematic frame id.

I second that this happens with direct calculations. In both cases, I have been using free databases (US LCA Commons, e.g.). So, I simply want to check what it looks like before going further. In the earlier versions, I used to get an error message (like 'out of memory'). These crashes happen for "ERROR | org.openlca.core.matrix.CalcExchange    | Formula evaluation failed, exchange 6393949". But it doesn't always crash.

I would also add that it doesn't always log in the log file. I have logs for Mar 11th and Mar 12th. And then Oct 03 2023. I have 20 hs_err_pid files over last 6 weeks. So, it didn't log for 5 months.

Am I missing any dependencies or such? Any help is appreciated.

Thanks,
Jignesh
by (220 points)
The source of my error was that some processes included in the modeled system had values of 0 for their output reference flows - finding those and getting rid of them solved my issues, so you could potentially start with looking for that.

1 Answer

0 votes
by (125k points)
These crashes typically come from a wrongly defined product system in your database, or an inconsistent database. If you validate the database, do you see any errors? Which database are you using? Do you see anything in the log file of openLCA? Thank you.
...