-
Notifications
You must be signed in to change notification settings - Fork 240
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Different results using SERIALIZER_TRACE_ERROR and SERIALIZER_NO_TRACE #12222
Labels
Comments
update for the people interested: in my case: I was adding each stage to a list something like: ` model = Kratos.Model()
this was causing the memory error. I do not understand why my simulation was working with: SERIALIZER_TRACE_ERROR though. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When im loading a derived class from set_moving_load_process from the StructuralMechanicsApplication with the kratos serializer, I get the message:
"MemoryError: bad array new length"
when im using SERIALIZER_NO_TRACE SerializerTraceType.
However when Im using the SerializerTraceType SERIALIZER_TRACE_ERROR, I do not have any problem and my simulation runs well.
Any idea what can cause this issue?
The text was updated successfully, but these errors were encountered: