Runtime Terminated in an Unusual Way for Longer Duration Simulation Times

[rbackhus@…]

Open Modelica is crashing when I run my model which includes Modelica_Synchronous blocks and a Normal Noise block. I get two message dialogs. The first one was a Microsoft Visual C++ Runtime Library dialog that said, "This application has requested the Runtime to terminate in an unusual way. Please contact the application's support team for more information." The second dialog was an OMEdit dialog that said, "OMEdit has stopped working. A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available."

I later discovered that when I simulate for 1 usec things run fine but when I simulate for 120 usec I get this crash.

The model source file, called SSD_PeakDetect, is contained in MyModelicaLibrary.mo which is attached.

The model parameters are as follows:

Pulse1 - amplitude=250.0E9, width=0.038, period=50.0E-6, nperiod=-1
NormalNoise1 - mu=0, sigma=1.4E-7, samplePeriod=1.0E-12
globalSeed - enableNoise=true
add3 - k1=1, k2=1
lowpassButterworth1 - n=2, f=4.5E6 Hz, y_start= 0
gain1 - k=2.4E6
periodClock1 - period=5.0E-9, useSolver=false
transferFunction1 - b={1}, a{=1, 0, 0}
add1 - k1=1, k2=1
transferFunction2 - b={1}, a={1,0}
add2 - k1=1, k2=1
transferFunction3 - b={1}, a={1, 0, 0, 0, 0, 0}

[sprl111]

Modelica source file for containing model

[rbackhus@…]

I forgot to include the simulation parameters.

Simulation Parameters are, Start Time = 0, Stop Time = 120.0E-6, Interval = 1.0E-12, Integration Method = dassl, Tolerence = 1E-6, Jacobian=coloredNumerical, DASSL Options = Root Finding & Restart After Event

[Martin Sjölund]

So you're doing 120 million output points. Roughly a 70GB result-file? 32-bit/64-bit OMC? Either way, OMEdit seems to be crashing when the file reaches 3.5GB...

[Martin Sjölund]

@Adeel: mOutputBuffer.append fails; even on 64-bit platforms; Qt seems to be limited to 32-bit Strings. The XML input needs to discard some of its input when reading, I suspect (so some kind of stream object, not strings)...

[Adeel Asghar]

We can get rid of this mOutputBuffer since I am only using it for internal debugging.
I will remove it.

[Adeel Asghar]

Try 34c440b/OMEdit.

[Adeel Asghar]

No response from the reporter.