Invalid node destroy command

Question

question

Nicholas B asked Nov 03 2017 at 8:30 PM Nicholas B answered Nov 16 2017 at 3:39 AM

Invalid node destroy command

I keep getting this error randomly and it is hard to replicate.

Software Version:

FlexSim HC 5.3.0

bug error message memory leak

· 5

Jeff Nordgren commented · Nov 08 2017 at 8:37 PM

@Nicholas B

You need to supply more information about the error, what is happening in the model and a way to reproduce it. Without your model for testing and eval, there is no way we can tell what is happening in your model or how to fix it. Any and all information you can give us would be helpful.

Thanks.

2 ·

Nicholas B commented · Nov 10 2017 at 12:58 PM

There literally is no way to reproduce it because it happens intermittently. I believe it is a memory leak somewhere, but I am just guessing at this point. This error had not popped up since I posted and then last night I got the error.

0 ·

Ben Wilson ♦♦ Nicholas B commented · Nov 10 2017 at 7:01 PM

@Nicholas B,

If you could provide the model, we could attempt to duplicate and debug.

If the model contains sensitive information, you could post it to a new, private question.

You might also look into making sure that your model is repeatable. This would help you narrow down what occurs to cause the error.

0 ·

Nicholas B commented · Nov 14 2017 at 5:34 PM

Here is the latest error message:

time: 75331.298581 exception: Exception Caught in getpreempt(treenode tasksequence) time: 75331.298581 exception: Exception caught in TreeNode::executememberfunctionwithexceptionhandling() c++/dll execution. Throwing... MAIN:/project/exec/usercommandlist/HC/StandardSelectionPolicy/node c: MAIN:/project/exec/usercommandlist/HC/StandardSelectionPolicy/node thisClass: MAIN:/project/exec/usercommandlist/HC/StandardSelectionPolicy/node time: 75331.298581 exception: Exception caught in flexscript execution of MODEL:/Tech_Surgery>variables/passto line 101 instruction 12. Discontinuing execution. time: 75331.298581 exception: Exception caught in flexscript execution of MODEL:/Tech_Surgery>variables/passto line 101 instruction 12. Discontinuing execution.

The model crashes. I close out of the model. Open up the model again and everything works as normal. I really think there is some kind of memory leak. Don't ask to replicate it happens randomly.

0 ·

Ben Wilson ♦♦ Nicholas B commented · Nov 14 2017 at 5:53 PM

@Nicholas B, if the model is repeatable, it will fail at the same time, every time. Or at least it would help pinpoint where the model execution starts to differ across model runs, then debug that code where runs of the model diverge.

That first link contains suggestions and steps to ensure your model is repeatable. We would be happy to help you with this if you can share the model with us. This is how we we would debug your model if you send it in.

If you cannot send your model, you will need to make your model is repeatable on your own. That first link contains lots of things to check, and a process to go through using the Event Log to ensure it is repeatable.

Without the model, there is no way for us to debug the issue, and you will need to debug on your own, following the suggestions in both links. We are totally happy to help, but without being able to get into the model, we can't do more than offer suggestions, leaving the actual debugging to you.

If you can't share the model, and you don't feel confident in following these steps, please call your local FlexSim office. We can help over the phone or set up a web meeting.

0 ·

______

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 · 2017-11-16T03:39:34Z

Nicholas B answered Nov 16 2017 at 3:39 AM

So I was able to get a new error code following the crash:

"Warning: realloc failed: ByteBlock setsize size requested: 2035435776 current size 0"

Answer 2 · 2017-11-14T18:32:19Z

Nicholas B answered Nov 14 2017 at 6:32 PM

So unfortunately and I wish I could make it repeatable it is not. The error messages are always different and the time/code where it fails is different as well. There is also no randomness in the model so I could run the same model over and over again and never get the error. Then open up the model and will get an error. If I can narrow it down I will update.

Answer 3 · 2017-11-10T14:22:24Z

Joerg Vogel answered Nov 10 2017 at 2:22 PM Jacob Gillespie commented Nov 10 2017 at 7:16 PM

The classic command is

destroyobject(obj node)

with dot syntax if it is available:

treenode node.destroy()

· 1

question