I have a debug point in a custom code block of my model. When I run the model I can run up to the second time this debug point stops it. After the second stop, if I step to the next line the model stops responding and appears to increase it's memory use until it eventually closes. I am not sure if my computer is forcing it to close or if something in the program closes it.
I am hoping you can help me better understand the actual source of this crashing so I can correct it. The line of code that appears to trip it up is assigning a token label to an integer variable in the custom code block. From what I can see at a surface level, I can not understand why this would make the model crash as the token has a value assigned to that label. Older files I have run past this point with no issue and the latest changes I made (adding another Process Flow and some 3D objects) have no interaction with this point. In fact I assign a macro value that I use to turn the new additions "off" so there is nothing running from that process flow at the time of the crash.