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
{{ message }}
Repository navigation
Investigate memory problem while running unit tests linked with Emscripten #249
Run node ./unittest/pke_tests.js on a Ubuntu machine with 16GB or 32GB RAM
Unittests in src/pke/unittest/utckksrns/UnitTestCKKSrns.cpp (EVAL_FAST_ROTATION_41 and all others after it) and src/pke/unittest/utckksrns/UnitTestCKKSrnsSerialize.cpp (CONTEXT_WITH_SERTYPE) fail because of lack of memory. Example:
"Exception thrown from UnitTest_EvalFastRotation(): std::bad_alloc" for EVAL_FAST_ROTATION_41.
It is most likely because of the cryptocontext memory not cleared after the previous test cases (could be cryptocontext's static data members).
Added pr, wires the #1179 cache-clear helpers into ReleaseAllContexts so live contexts actually get cleared, and adds a trim path so freed memory returns to the OS.
This lets the EVAL_FAST_ROTATION_41–48 and CONTEXT_WITH_SERTYPE tests #985 had to disable run again under Emscripten without hitting the 4 GB WASM cap, closes #249. No hot-path file touched.
Activity
BAder82t commentedon Jun 18, 2026
Added pr, wires the #1179 cache-clear helpers into
ReleaseAllContextsso live contexts actually get cleared, and adds a trim path so freed memory returns to the OS.This lets the
EVAL_FAST_ROTATION_41–48andCONTEXT_WITH_SERTYPEtests #985 had to disable run again under Emscripten without hitting the 4 GB WASM cap, closes #249. No hot-path file touched.fix: close issue #249 — Emscripten OOM in CKKS unit tests
fix: close issue #249 — Emscripten OOM in CKKS unit tests
Run the same unit tests under Emscripten as natively
fix: close issue #249 — Emscripten OOM in CKKS unit tests
Run the same unit tests under Emscripten as natively
fix: close issue #249 — Emscripten OOM in CKKS unit tests (#1215)