Opened 8 years ago

Closed 18 months ago

#2745 closed defect (fixed)

Stack overflow detected and was not caught

Reported by: bitelxux Owned by: perost
Priority: high Milestone: 1.16.0
Component: New Instantiation Version: trunk
Keywords: Cc:


Buildings examples breaks omc.

  • OpenModelica 1.9.1+dev (r21395) (RML version)
  • Linux 3.11.0-12-generic #19-Ubuntu SMP Wed Oct 9 16:12:00 UTC 2013 i686 i686 i686 GNU/Linux
  • 4Gb RAM
  • /usr/lib/omlibrary/Buildings latest/Examples/Tutorial/SpaceCooling/System3.m
  • /usr/lib/omlibrary/Buildings latest/Examples/Tutorial/SpaceCooling/System2.m

Attachments (2) (1.5 MB) - added by bitelxux 8 years ago.
omc-bootstrap output (1.4 KB) - added by perost 8 years ago.
Minimal model of System2

Download all attachments as: .zip

Change History (14)

Changed 8 years ago by bitelxux

omc-bootstrap output

comment:1 Changed 8 years ago by

  • Component changed from Unknown to Frontend
  • Owner changed from somebody to perost
  • Status changed from new to assigned

Changed 8 years ago by perost

Minimal model of System2

comment:2 Changed 8 years ago by perost

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 Changed 8 years ago by

The minimal one is still causing a stack overflow with Adrian's changes. The total model version from current is working fine though.

comment:4 Changed 8 years ago by

  • Milestone changed from 1.9.1 to 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 Changed 7 years ago by

  • Milestone changed from 1.9.2 to 1.9.3

Milestone changed to 1.9.3 since 1.9.2 was released.

comment:6 Changed 7 years ago by

  • Milestone changed from 1.9.3 to 1.9.4

Moved to new milestone 1.9.4

comment:7 Changed 6 years ago by

  • Milestone changed from 1.9.4 to 1.9.5

Milestone pushed to 1.9.5

comment:8 Changed 6 years ago by

  • Milestone changed from 1.9.5 to 1.10.0

Milestone renamed

comment:9 Changed 5 years ago by

  • Milestone changed from 1.10.0 to 1.11.0

Ticket retargeted after milestone closed

comment:10 Changed 5 years ago by

  • Milestone changed from 1.11.0 to 1.12.0

Milestone moved to 1.12.0 due to 1.11.0 already being released.

comment:11 Changed 5 years ago by casella

  • Milestone changed from 1.12.0 to 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 Changed 18 months ago by perost

  • Component changed from Frontend to New Instantiation
  • Milestone changed from Future to 1.16.0
  • Resolution set to fixed
  • Status changed from assigned to closed

Still an issue in the old frontend, but the new frontend works fine.

Note: See TracTickets for help on using tickets.