Opened 10 years ago
Closed 4 years ago
#2745 closed defect (fixed)
Stack overflow detected and was not caught
Reported by: | bitelxux | Owned by: | Per Östlund |
---|---|---|---|
Priority: | high | Milestone: | 1.16.0 |
Component: | New Instantiation | Version: | trunk |
Keywords: | Cc: |
Description
Buildings examples breaks omc.
Attachments (2)
Change History (14)
by , 10 years ago
Attachment: | omc.fail.txt added |
---|
comment:1 by , 10 years ago
Component: | Unknown → Frontend |
---|---|
Owner: | changed from | to
Status: | new → assigned |
comment:2 by , 10 years ago
I made a minimal model of System2 that triggers the stack overflow. MoistAirUnsaturated contains lots of relative self-references, i.e. Buildings.Media.GasesPTDecoupled.MoistAirUnsaturated.specificEnthalpy calls Buildings.Media.GasesPTDecoupled.MoistAirUnsaturated.h_pTX instead of simply h_pTX. I don't know why this style is used, it's the same with the MSL, since it leads to slower lookup and makes it harder to reuse models. But it seems that this creates some issues coupled with the redeclares. We'll probably have to wait for Adrian's new frontend stuff before this can be fixed.
Removing the unnecessary self-references from MoistAirUnsaturated avoid the stack overflow, but the compiler instead segfaults while trying to constant evaluate Buildings.Fluid.MixingVolumes.MixingVolume.Medium.specificEnthalpy_pTX. I suspect it's because of more redeclare issues, but I haven't looked into this yet.
comment:3 by , 10 years ago
The minimal one is still causing a stack overflow with Adrian's changes. The total model version from current System2.mo is working fine though.
comment:4 by , 10 years ago
Milestone: | 1.9.1 → 1.9.2 |
---|
This ticket was not closed for 1.9.1, which has now been released. It was batch modified for milestone 1.9.2 (but maybe an empty milestone was more appropriate; feel free to change it).
comment:5 by , 10 years ago
Milestone: | 1.9.2 → 1.9.3 |
---|
Milestone changed to 1.9.3 since 1.9.2 was released.
comment:10 by , 8 years ago
Milestone: | 1.11.0 → 1.12.0 |
---|
Milestone moved to 1.12.0 due to 1.11.0 already being released.
comment:11 by , 7 years ago
Milestone: | 1.12.0 → Future |
---|
The milestone of this ticket has been reassigned to "Future".
If you think the issue is still valid and relevant for you, please select milestone 1.13.0 for back-end, code generation and run-time issues, or 2.0.0 for front-end issues.
If you are aware that the problem is no longer present, please select the milestone corresponding to the version of OMC you used to check that, and set the status to "worksforme".
In both cases, a short informative comment would be welcome.
comment:12 by , 4 years ago
Component: | Frontend → New Instantiation |
---|---|
Milestone: | Future → 1.16.0 |
Resolution: | → fixed |
Status: | assigned → closed |
Still an issue in the old frontend, but the new frontend works fine.
omc-bootstrap output