You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To an extent, however, the memory usage is expected. The memory (m) used by the analyzer is a function of the number of values (n) and the complexity of those values (c), which is dependent on the contract as follows:
$$
\text{m} \propto n \cdot c
$$
While there are refactors that can be done to reduce the "memory load" of each individual value, this fundamental relation will still remain.
Describe the Bug
Certain contracts use a lot of memory.
Setup
maximum_iterations_per_opcode=10
andmaximum_forks_per_fork_target=25
To Reproduce
Steps to reproduce the behavior:
Run one of the following contracts
MeTokenRegistryFacet
Below is the memory usage over time, it can be seen it maxes out at ~7.5gb.
CapsulesTypeface
Below is the memory usage over time, it can be seen it maxes out at ~4.8gb.
BorrowLogic
Below is the memory usage over time, it can be seen it maxes out at ~3gb.
CpuFrilessVerifier
Below is the memory usage over time, it can be seen it maxes out at ~2.5gb.
Expected Behaviour
Less memory to be used.
The text was updated successfully, but these errors were encountered: