Skip to content

Fix for cbmc running out of memory while printing traces using json_ui #1767

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

Closed

Conversation

NlightNFotis
Copy link
Contributor

There has been a bug reported to us where cbmc would run out of memory while creating a huge json object in memory to report the traces with. This is changing the tracing report facility to use a new json class that streams the objects immediately as created, and therefore fixes the issue.

@peterschrammel
Copy link
Member

@NlightNFotis, do you have evidence that this now indeed fixes/mitigates the problem?

@peterschrammel
Copy link
Member

As discussed directly, to avoid conflicts with the current rebasing efforts, I will not make a PR for thejson_streamt refactoring for develop. It will hit develop through goto-analzyer-develop (merge expected to happen in March).

@martin-cs
Copy link
Collaborator

Follow-up from chatting with @peterschrammel and @NlightNFotis : goto-analyzer-develop will not be directly merged, so a PR against develop would be good as well.

@NlightNFotis
Copy link
Contributor Author

This was the first attempt at solving the problem with jsont causing out of memory problems while printing some traces. It has been superseded by #1814 which is now merged, therefore this PR should now be able to be closed without any issues.

@NlightNFotis NlightNFotis deleted the peter-json-fix branch October 20, 2020 15:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants