Skip to content
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

CVC4 causes segmentation faults when used from original repo. #169

Closed
kfriedberger opened this issue Nov 2, 2019 · 1 comment
Closed

Comments

@kfriedberger
Copy link
Member

kfriedberger commented Nov 2, 2019

We currently use a modified version of CVC4 from https://github.com/kfriedberger/CVC4 where all finalizers are disabled to avoid several SegFaults. The problem appears sometimes on Java8 and more often on Java11. The original issue can be found at cvc5/cvc5#2846.
With all finalizers disabled, we do not have memory cleanup of CVC4 objects and leak memory as soon as the Java wrapper for such an CVC4 object is removed.

Possible steps to improve this:

  • find the cause why finalizers are not working.
  • replace finalizers by some management of WeakReferences like in other parts of our software.
  • optimal solution: integrate our solution into the original CVC4 repository and avoid using and maintaining our own repository.
@kfriedberger
Copy link
Member Author

CVC4 is superseeded by CVC5. JavaSMT will support both solvers for some time and then drop support for CVC4.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

1 participant