Opened 7 years ago

Closed 7 years ago

#4558 closed defect (fixed)

stackoverflow not caught

Reported by: Matthis Thorade <m.thorade@…> Owned by: Per Östlund
Priority: high Milestone: 2.0.0
Component: New Instantiation Version:
Keywords: HelmholtzMedia Cc:

Description

When simulating the Butane models from HelmholtzMedia:
https://libraries.openmodelica.org/branches/master/HelmholtzMedia/files/HelmholtzMedia_HelmholtzMedia.Examples.MediaTestModels.ButaneTestModel_dT.err

The 1.12 beta2 64bit on Windows crashes OMEdit, on Linux with the 1.13 nightly OMEdit does not crash, but does display the message:

[3] 17:11:57 Scripting Error
Stack overflow detected and was not caught.
Send us a bug report at https://trac.openmodelica.org/OpenModelica/newticket
    Include the following trace:
[bt] Execution path:

Attachments (1)

ButaneTestModel_dT.mo (727 bytes ) - added by Per Östlund 7 years ago.
Minimal test model

Download all attachments as: .zip

Change History (5)

by Per Östlund, 7 years ago

Attachment: ButaneTestModel_dT.mo added

Minimal test model

comment:1 by Per Östlund, 7 years ago

Component: *unknown*New Instantiation
Milestone: Future2.0.0
Owner: changed from somebody to Per Östlund

I added a minimal model in case anyone wants to look into this, but this looks like precisely the kind of issue that's the reason why we're working on a new frontend. Note that the minimal model is so minimal that it's not actually a valid model anymore, but it still gives the same stack overflow.

comment:2 by Martin Sjölund, 7 years ago

With -d=-scodeDep you get further, but it still gets a stack overflow.

comment:3 by Francesco Casella, 7 years ago

With the NF, the flattening currently stops here

[Modelica 3.2.2/Media/package.mo:7196:9-7196:41:writable] Notification: From here:
[OMCompiler/build/lib/omlibrary/HelmholtzMedia/Interfaces/PartialHelmholtzMedium/package.mo:546:5-546:56:writable]
Error: Constant fluidConstants[1].molarMass is used without having been given a value.

This is actually the same issue reported in #4918, so I would consider the original issue of this ticket solved for 2.0.0 (i.e. assuming you will use the new front-end).

Last edited 7 years ago by Francesco Casella (previous) (diff)

comment:4 by Francesco Casella, 7 years ago

Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.