invalid node insert_bareBones command

Question

question

Sung K2 asked Oct 4, '20 Sung K2 commented Oct 7, '20

invalid node insert_bareBones command

My model gives me "invalid node insert_bareBones command". Anyone who know what this means?

I found some other posts for similar error messages like "invalid node destroy command" or "invalid node insert command", but no clue for my error found.

As one of the posts mentioned about memory leaking, coincidently, my memory was also creeping up to almost all memory (~98% of 16GB). Also, similar to "Anna Dierking"'s post, the error happens at random sim time, but always happens around the peak memory consumption.

I am not sure how it is related but, from half of the error incidents, my computer crashes and frozen, need to be reboot. Some incidents, not frozen, but can't open outlook, or copy &paste, or open other office programs... even the start button doesn't do anything...

The model is originally built in 2020 update 1, and same error occurs when I use 2020 update 2.

Anyone who has any clue? I would appreciate any inputs.

Software Version:

FlexSim 20.2.1

flexsim 20.2.1 barebones

1601771466653.png (28.0 KiB)

Answer 1 · 2020-10-06T15:17:50Z

Phil BoBo answered Oct 6, '20 Sung K2 commented Oct 7, '20

That message means that an error occurred while trying to create a treenode. That could be caused by just about anything anywhere in your model.

Without a model to debug, we can't explain what is happening. Try using the Memory Profiler from the Debug menu to determine what is taking up so much memory in your model.

If you can't figure out what is happening, you may need to post your model in a private question so that we can debug it to determine what is happening.

· 1

Sung K2 commented · Oct 07, 2020 at 08:14 PM

Thank you, BoBo!!
I didn't notice the cool feature, Memory Profiler! :)

It shows significant grow in FlowItemBin subtree. It reminds that I set recycling flowitem option (hoping that it speeds up the runtime...) So, I tried to remove the recycling option (thinking that it might have something to do with taking up the memory), and it works!! No more growing. Interestingly, I don't feel much difference of the runtime speed. I am glad that my model runs successfully without crash!

Thanks much again for your help!!

1 ·

1602101644231.png (44.0 KiB)

question