Too many calls to getContainer() cause an out-of-memory error from Emscripten

[NyuBlara]

The Chronology class's getContainer() accessor returns a reference to the chronology's container. Despite the lightweight nature of references, and even though no allocation takes place, running the library in some environments, such as Emscripten, will, after too many calls to this accessor, raise an out-of-memory error. The following screenshot is from the Web-MFP console :

The most likely hypothesis (provided after a discussion with a friend, @CLOVIS-AI) might be that this is actually a stack overflow, reported as an OOM because WebAssembly's memory object is a single buffer containing both stack and heap.

Even so, this gives very few leads as to how to mitigate the issue, since returning a copy of the container would occupy more space and thus lead to an even faster overflow.