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
Maybe I'm reading this wrong, but doesn't OutOfMemory() always return true?
/// - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
/** Used to check if we have enough memory to start a new node process
* This is used to prevent node from starting too many processes.
*/
function OutOfMemory() {
const bytesToMB = 1024 * 1024;
let free = os.freemem() / bytesToMB; // mb
const warnMem = SYSMEM_MIN;
const critMem = SYSMEM_MIN / 4;
const low = free < critMem;
const warn = free < warnMem;
if (low) return `**CRITICAL** (< crit fail buffer ${critMem}MB)`;
if (warn) return `**WARNING** (< mem buffer ${warnMem}MB`;
return `OK (>${SYSMEM_MIN}MB free)`;
}
So while RenderMemoryReport() is correctly using OutOfMemory() to retrieve a message, m_RouterLogic():833 is relying on OutOfMemory() to return true or false.
The text was updated successfully, but these errors were encountered:
After merging #7,
In spite of having plenty of memory (e.g. here there's 582MB)...
Opening a saved graph always results in an out of memory error:
To Replicate
Ran out of Memory. Can't start the graph.
error.Investigating
Maybe I'm reading this wrong, but doesn't
OutOfMemory()
always return true?So while
RenderMemoryReport()
is correctly usingOutOfMemory()
to retrieve a message,m_RouterLogic():833
is relying onOutOfMemory()
to return true or false.The text was updated successfully, but these errors were encountered: