-
Notifications
You must be signed in to change notification settings - Fork 25
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
Problem in proof writing #81
Comments
Which proofs? After being processed by which algorithms? |
I've written a comment to the mailing list - would it've been better off here? |
Yes. It is better to try to keep the issues in the issue tracker self-contained... But if something needs a long discussion, it is ok to discuss in the mailing-list. |
The problem happens in my laptop too:
|
Is this the smallest proof for which this problem occurs for you, Andreas? |
I had a small list of possibly bad proofs. This is just one - I will try the other ones and see which one is the smallest |
Just send me the smallest file (in kiloBytes)... |
I think I have identified the problem. This proof contains an expression that is so big that the heap space is exhausted while this formula is converted to a string. Formulas are represented as DAGs in the memory, but our naive toString method expands the DAGs to trees. The string representation of the tree expansion of the expression is too big for the heap. We need a less naive way to output expressions to files. Among other things, it should name and reuse subexpressions, as is already done by VeriT in the proofs it provides to us. I will think more about how to solve this issue elegantly. |
some proofs produce heap space errors when being written to a file
The text was updated successfully, but these errors were encountered: