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
As shown by status-im/nimbus-eth2#370 (comment), putting too much data on the stack will have serious impact on the GC as it scans it to find live objects (100x slowdown).
It seems like libsecp256k1 uses the stack a lot as well. The dependency should be updated after bitcoin-core/secp256k1#692 is fixed.
The text was updated successfully, but these errors were encountered:
bitcoin-core/secp256k1#692 only applies to a weird non-defaultconfiguration that I expect nothing is actually using. The library doesn't otherwise use a large amount of information on the stack
The stack-scanning done by Nimbus GC does affect nimbus-eth1 when the EVM runs and uses a lot of stack.
Recent changes (shown above) have fixed stack usage in the EVM, so this is no longer a problem.
There may be other causes of substantial stack use, e.g. I haven't checked if libsecp256k1 does, mentioned above.
Therefore keeping this issue open until that's been checked.
As shown by status-im/nimbus-eth2#370 (comment), putting too much data on the stack will have serious impact on the GC as it scans it to find live objects (100x slowdown).
It seems like libsecp256k1 uses the stack a lot as well. The dependency should be updated after bitcoin-core/secp256k1#692 is fixed.
The text was updated successfully, but these errors were encountered: