Staytime chart hanging issue

Question

question

Jon Abbott asked May 22 2020 at 6:31 PM Jordan Johnson commented May 28 2020 at 8:08 PM

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

Software Version:

FlexSim 20.1.2

flexsim 20.1.2 bug staytime hang

example-model-2.fsm (28.0 KiB)

______

Cookie preferences

Your privacy is important to us and so is an optimal experience. To help us customize information and build applications, we collect data about your use of this site.

May we collect and use your data?

Learn more about the Third Party Services we use and our Privacy Statement.

Strictly necessary – required for our site to work and to provide services to you

These cookies allow us to record your preferences or login information, respond to your requests or fulfill items in your shopping cart.

YES

Improve your experience – allows us to show you what is relevant to you

These cookies enable us to provide enhanced functionality and personalization. They may be set by us or by third party providers whose services we use to deliver information and experiences tailored to you. If you do not allow these cookies, some or all of these services may not be available for you.

YES

NO

Customize your advertising – permits us to offer targeted advertising to you

These cookies collect data about you based on your activities and interests in order to show you relevant ads and to track effectiveness. By collecting this data, the ads you see will be more tailored to your interests. If you do not allow these cookies, you will experience less targeted advertising.

YES

NO

Are you sure you want a less customized experience?

We can access your data only if you select "yes" for the categories on the previous screen. This lets us tailor our marketing so that it's more relevant for you. You can change your settings at any time by visiting our privacy statement

Your experience. Your choice.

We care about your privacy. The data we collect helps us understand how you use our products, what information you might be interested in, and what we can improve to make your engagement with Autodesk more rewarding.

May we collect and use your data to tailor your experience?

Explore the benefits of a customized experience by managing your privacy settings for this site or visit our Privacy Statement to learn more about your options.

Answer 1 · 2020-05-27T23:14:30Z

Jordan Johnson answered May 27 2020 at 11:14 PM Jordan Johnson commented May 28 2020 at 8:08 PM

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

Jon Abbott commented · May 27 2020 at 11:33 PM

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

0 ·

Jon Abbott Jon Abbott commented · May 28 2020 at 12:11 AM

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 ·

Jordan Johnson ♦♦ Jon Abbott commented · May 28 2020 at 8:08 PM

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 ·

question