emscripten-core/emscripten

Memory leak during repeated runs on node.js?

Open

#12,740 opened on Nov 9, 2020

View on GitHub
 (15 comments) (1 reaction) (0 assignees)C++ (3,519 forks)batch import
good first bughelp wanted

Repository metrics

Stars
 (27,361 stars)
PR merge metrics
 (Avg merge 19d 10h) (147 merged PRs in 30d)

Description

Running on node v14.8.0, when I run the same emscripten function repeatedly I eventually run out of memory. Here's a gist that shows the memory ticking up by 16MB each run for a minimal C file that doesn't allocate any memory: https://gist.github.com/apowers313/cee96b41e1f3ba272b214fc7e1c983bb

Contributor guide

Research direction
Run the provided gist locally, monitor memory usage with Node.js heap snapshots, and identify which objects persist across runs. Investigate whether Emscripten's memory management (e.g., totalMemory, ALLOW MEMORY GROWTH) is causing the leak.
Tech stack
javascriptcpp
Domain
backend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
JavaScriptNode.js
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75