question

Laurenz Peleman avatar image
0 Likes"
Laurenz Peleman asked Laurenz Peleman answered

Error Stack Overflow DestroyPartitionEvent

Hello everyone

I encountered a stack overflow error, which is probably caused by an accumulation of DeadPartitionEvents in my Event List.

The cause of this behaviour is a nested loop of Acquire Resource activities where we successfully acquire the QuayConveyors resource (see figure) in the first stage, but have to release it when acquiring other objects in the second didn't succeed. However, releasing does not seem to execute the DestroyPartitionEvent which pops up in the Event List, so that, if we try to assign a new QuayConveyors resource in a next activity (without delays in between), a new DestroyPartitionEvent is created, and so on. Since we do a high amount of loops (> 10), the list of DestroyPartitionEvents becomes so large it ultimately causes a Stack Overflow Error, and hence the model crashes.

Is this normal behaviour of Flexsim or have we done something that causes these events to pile up?

Kind regards

Laurenz Peleman

FlexSim 17.1.6
stack overflow
deadpartition.png (127.7 KiB)
5 |100000

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

Jeff Nordgren avatar image
0 Likes"
Jeff Nordgren answered Laurenz Peleman commented
@Laurenz Peleman

To be able to verify that it can be duplicated, we need to be able to look at the model file that is causing the problem. If you need to mark your question as "Private" to be able to send your model, please do that in another question, marking it private. That way only FlexSim will be able to see your question.

Thanks.

5 |100000

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

Laurenz Peleman avatar image
0 Likes"
Laurenz Peleman answered

@Jeff Nordgren

I sent the model in a private question some days ago, have you already been able to identify the problem?

Kind regards

5 |100000

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