question

Jon Abbott avatar image
0 Likes"
Jon Abbott asked Jordan Johnson commented

Staytime chart hanging issue

I have encountered what appears to be a bug in Staytime charts in FlexSim 20.1.2. It causes the application to hang and enter a memory allocation runaway condition. Please try running the attached model. If it doesn't hang, stop and reset the model, then try running it a few more times. It usually hangs within five tries. It only appears to happen when "Repeat random streams" is disabled. After the hang happens, Task Manager can be used to see that the FlexSim process consumes all available system memory in less than a minute. I then do End Task to prevent it from crashing the system. Thanks in advance for your assistance.

Example Model 2.fsm

FlexSim 20.1.2
flexsim 20.1.2bugstaytimehang
example-model-2.fsm (28.0 KiB)
5 |100000
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

1 Answer

Jordan Johnson avatar image
0 Likes"
Jordan Johnson answered Jordan Johnson commented
I was able to replicate this on my computer. That's a bad bug, and I'll get it on the dev list. I haven't figured out a workaround yet, but I'll let you know if I do.
· 3
5 |100000
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

Jon Abbott avatar image Jon Abbott commented ·

Thanks, @Jordan! That's great that you were able to replicate the issue.

0 Likes 0 ·
Jon Abbott avatar image Jon Abbott Jon Abbott commented ·

By the way @Jordan, this appears to happen with FlexSim 20.0 as well. If I had to guess, the fixed process time seems to lead to this chart hanging. If I use uniform(10,10.0001) as the process time instead, it doesn't seem to ever hang. Another curiosity is that if you set the process time to 10 and run it for a while without it hanging, it will sometimes show multiple bars in the histogram, even though there is only one process time value.

0 Likes 0 ·
Jordan Johnson avatar image Jordan Johnson ♦♦ Jon Abbott commented ·

In regard to the "mutliple values" question, it depends on your bar boundaries, and on floating point precision. If an item enters the processor at time t1, and the process time is 10, then it exits at time t2. We calculate staytime as t2 - t1, which sometimes has a very slight precision error, 10.000000000001 or something like that, rather than 10.0 exactly.

0 Likes 0 ·