OCaml 5 memory blowup workaround #802
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This commits try to workaround a memory blowup in Why3 by changing the `space_overhead` configuration of the GC before calling SMT solvers. This hack should be removed once the root cause has been found and fixed. Time impact is limited (< 1%).
strub
force-pushed
the
ocaml5-why3-mem
branch
from
c6ffad1 to
a21665e
Compare
|
See #740 for the CI. |
fdupress
approved these changes
Sep 2, 2025
|
No, the impact is limited of SMT heavy source code. |
|
Merging as #740 is green (before this patch, some projects were OOM killed). Regarding timing, in general, we are more at 10% in general but for a temporary workaround, this is ok, given that we do not have any memory blowup anymore:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commits try to workaround a memory blowup in Why3 by changing the
space_overheadconfiguration of the GC before calling SMT solvers.This hack should be removed once the root cause has been found and fixed.
Time impact is limited (< 1%).