Opened 4 years ago
Last modified 4 years ago
#6430 new defect
Error -1073741819 at solving initiation (after complete compilation)
Reported by: | Owned by: | somebody | |
---|---|---|---|
Priority: | high | Milestone: | NeedsInput |
Component: | *unknown* | Version: | 1.18.0-dev |
Keywords: | Cc: |
Description
Hi,
We encounter a stranger error called -1073741819 on Windows x64. It appears in the "Output" tab in the Simulation windows. The full message is (in red) :
"Process crashed
Process crashed
Simulation process failed. Exited with code -1073741819. "
The model working on several computers makes a crash on one computer. Different OpenModelica version were tested on this machine and error is the same.
Attachments (3)
Change History (8)
by , 4 years ago
follow-up: 2 comment:1 by , 4 years ago
OK, we really need to do something with these exit codes, see #6242. Basically, the error is an exadecimal 32 bit code which is printed out as a signed integer, making it completely unrecognizable. If you add 232 and convert it to hex it becomes 0xC0000005, or binary 0b11000000000000000000000000000101, which only has four non-zero bits and make a lot more sense.
Error codes are available here. It means STATUS_ACCESS_VIOLATION, probably some memory was accessed illegally.
If the error can be somewhat reproduced, it would be useful to get a model to test it ourselves with gdb, to try pinpointing the root cause.
comment:2 by , 4 years ago
comment:4 by , 4 years ago
Thank you for your replies.
We are trying to find the missing dll and we will give you a feedback on this error.
comment:5 by , 4 years ago
Hi OpenModelica team,
We succeeded in finding the bug origin. We made a simplified model to explain the error (see "ErrorSimpleModel.mo"). On one specific machine (system information are given in "SystemINformation.pdf"), we have the error code -1073741819 ("STATUS_ACCESS_VIOLATION") in the "Output" tab in the Simulation windows when the Medium is Modelica.Media.Air.DryAirNasa, but it works with ReferenceAir.Air_dT (and also with SimpleAir).
So we will switch to ReferenceAir. If you manage (to spend time) to reproduce the error and to understand it, we are interested in it.
Thank you for your works
Error description