Opened 4 years ago
Closed 3 years ago
#5669 closed defect (fixed)
OMEdit crashes expanding Modelica.Media.Air
Reported by: | adeas31 | Owned by: | adrpo |
---|---|---|---|
Priority: | blocker | Milestone: | 1.19.0 |
Component: | NF API | Version: | |
Keywords: | Cc: | sjoelund.se |
Description
Start OMEdit, expand to Modelica.Media.Air. Crash!
I looked at the log file and it crashes calling getInheritedClasses(Modelica.Media.Air.ReferenceMoistAir). Here is output from gdb,
Thread 1 received signal SIGSEGV, Segmentation fault. 0x0000000014ee0ef4 in omc_InstExtends_instClassExtendsList2 ( threadData=threadData@entry=0x0, _inEnv=_inEnv@entry=0x0, _inMod=<optimized out>, _inName=<optimized out>, _inClassExtendsElt=0xd8ba96c3, _inElements=0xf727d703, out_outElements=0x95e4528, out_outElements@entry=0x95e4560) at C:/OpenModelica/OMCompiler/Compiler/boot/build/tmp/InstExtends.c:4764 4764 tmp4 = 0;
Also getInheritedClasses is very slow in some cases take a look at getInheritedClasses(Modelica.Media.Air.SimpleAir) and getInheritedClasses(Modelica.Media.Air.DryAirNasa). Can you update it to use the NF.
Change History (13)
comment:1 Changed 4 years ago by casella
- Milestone changed from 1.14.0 to 1.15.0
comment:2 Changed 4 years ago by adeas31
See #5803.
comment:3 Changed 4 years ago by casella
- Milestone changed from 1.15.0 to 1.16.0
Release 1.15.0 was scrapped, because replaceable support eventually turned out to be more easily implemented in 1.16.0. Hence, all 1.15.0 tickets are rescheduled to 1.16.0
comment:4 Changed 4 years ago by Kossong <nruchti@…>
I get the same/similar crash on 1.16.0. I Run Windows 7 64 bit.
While Loading Modelica.Media.Air it crashes either on DryAirNasa or on ReferenceMoistAir which will be loaded aftewerard.
From the ressource monitor I noticed that the RAM rises continously until windows shows up the Modal window "OMEdit don't work any more" to kill it.
I'm not a programmer. So contact me if you want to make diagnostics.
comment:5 Changed 4 years ago by casella
@nruchti, if you find any specific issue that is not already covered by a ticket and you can reproduce it, please open a ticket describing it. This is very much appreciated.
comment:6 Changed 4 years ago by anonymous
Is this a duplicate to #5575 ?
Ulrich
comment:7 Changed 4 years ago by adeas31
Not really. This ticket is about a crash and #5575 is about the performance. However, both are because of same API.
comment:8 Changed 3 years ago by casella
- Milestone changed from 1.16.0 to 1.17.0
Retargeted to 1.17.0 after 1.16.0 release
comment:9 Changed 3 years ago by casella
- Milestone changed from 1.17.0 to 1.18.0
Retargeted to 1.18.0 after 1.17.0-dev.beta2 release
comment:10 Changed 3 years ago by casella
- Milestone 1.18.0 deleted
Ticket retargeted after milestone closed
comment:11 Changed 3 years ago by casella
- Milestone set to 1.19.0
1.18.0 blocker tickets moved to 1.19.0
comment:12 Changed 3 years ago by perost
Fixed in 9e0e8de8.
comment:13 Changed 3 years ago by perost
- Resolution set to fixed
- Status changed from new to closed
Releasing 1.14.0 which is stable and has many improvements w.r.t. 1.13.2.
This issue, previously marked as blocker for 1.14.0, is rescheduled to 1.15.0