That's good to hear. Don't hesitate to tell us about your application in case you think that the kind of string processing you were doing could be of general interest – requests like that are important for setting the right priorities for future product development.

I see. System Modeler currently only has basic support for strings, and it sounds as if your approach might require a more complete solution for string handling. If this is the case, it is something we see very rarely – is there any chance that the "heavy" string processing could be lifted also out of your model?

The Dynamic assert strings setting was introduced to avoid a performance problem which is now handled using better code generation instead. However, the setting happened to also provide a workaround for hitting the string size constraints in the context of asserts, and for this there is currently no replacement for the setting.

Without knowing more about your particular model, it is not clear whether the problems are related to asserts, or what could be the source of the large strings. To better understand what workarounds one could try or how the product could be improved it would be interesting to know more about your model, such as the type of the added component.

OK, it's good that you can confirm that this is the problem that the Dynamic assert strings setting was meant to address. Then, of course, it's too bad that it didn't solve your problems for the larger system. It is a known issue that the user can't change the size of the memory used to hold strings during expression evaluation, and I'm adding you as a reporter of this.

I just checked this in Windows (I had found discrepancies between the OS versions in the past). I am getting the same error. It happens with the ideal gas components, but not with Air. I'm going to tag @Ankit Naik and @Jan Brugard to see if they have any ideas

Did you try turning off Dynamic assert strings under Preferences -> General -> Translation?