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
Is your feature request related to a problem? Please describe.
Currently, memory that has been allocated and not released is often retained by the current process. While this can benefit the same process when it mallocs more memory (re-usage), it doesn't help other processes, including a new main process during a reload. As a result, the system may be inefficient in terms of memory utilization across reloads.
Describe the solution you'd like
Before every reload attempt, the main process should call malloc_trim(3) if available to release unused memory back to the system. This would allow the system to free up memory that may no longer be needed, helping with overall memory efficiency and preventing wasted space for other processes, including newly spawned ones.
Is your feature request related to a problem? Please describe.
Currently, memory that has been allocated and not released is often retained by the current process. While this can benefit the same process when it mallocs more memory (re-usage), it doesn't help other processes, including a new main process during a reload. As a result, the system may be inefficient in terms of memory utilization across reloads.
Describe the solution you'd like
Before every reload attempt, the main process should call
malloc_trim(3)
if available to release unused memory back to the system. This would allow the system to free up memory that may no longer be needed, helping with overall memory efficiency and preventing wasted space for other processes, including newly spawned ones.Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered: