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
While profiling gnark during compilation and proof phaze I noticed that AttachDebugInfo and in turn NewDebugInfo contribute to large (if not the largest) portion of memory. In my case it was 500mb out of 800.
Expected Behavior
Do not create anything in NewDebugInfo if debug.Debug is set to false
Actual Behavior
NewDebugInfo() contributes to memory growth regardless of debug.Debug const value
Description
While profiling gnark during compilation and proof phaze I noticed that
AttachDebugInfo
and in turnNewDebugInfo
contribute to large (if not the largest) portion of memory. In my case it was 500mb out of 800.Expected Behavior
Do not create anything in
NewDebugInfo
ifdebug.Debug
is set tofalse
Actual Behavior
NewDebugInfo() contributes to memory growth regardless of
debug.Debug
const valuePossible Fix
smth like
would do the job
Context
We are planning to run gnark on mobile devices where memory consumption turns to be critical
Your Environment
The text was updated successfully, but these errors were encountered: